Related
I've recently rooted my G Tablet and installed CM 7 rc1 and I'm running into a weird issue. If I plug my G tab into a computer the computer will make the connection noise, say it's installing drivers and say all is good. Problem is that the G tab doesn't see that it's connected and I neither does my computer. Other issue is with the microSD. The G tablet doesn't see it. I know the card is good my testing it in other devices. Recovery doesn't see it either. All I can access is the internal memory. Also on an interesting note. If I use recovery to turn on mass storage the computer see it then and I can move files.
I promise I dug trying ti find this so if a thread already exists point me there and I'll be on my way. Other wise thanks for the help.
chip17 said:
If I plug my G tab into a computer the computer will make the connection noise, say it's installing drivers and say all is good. Problem is that the G tab doesn't see that it's connected and I neither does my computer.
Click to expand...
Click to collapse
Try playing with the "USB debugging" and "USB debugging notify" settings in Settings > Applications > Development.
Other issue is with the microSD. The G tablet doesn't see it.
Click to expand...
Click to collapse
Plug your microSD in, then open a Terminal Emulator window and get me a dmesg output. Use the commands in this post.
Also include the output of the mount command. Again, in a Terminal window:
Code:
$ [B]mount | tee /mnt/sdcard/mount.txt[/B]
Only type in the commands in bold. The rest of the stuff is just there to show you how the screen will generally look.
Here's the second command return....
As you can see I tried the first one no return. Will try again see if I had a syntax error.
$ export PATH=/data/local/bin:$PATH
$su
#dmesg >/mnt/sdcard/dmesg.txt
# logcat -d -v time >/mnt/sdcard/logcat.txt
# mount | tee /mnt/sdcard/mount.txt
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk3p2 on /data type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:25 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/emmc type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/com.androirc-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
chip17 said:
Here's the second command return....
As you can see I tried the first one no return. Will try again see if I had a syntax error.
Click to expand...
Click to collapse
There is no syntax error. You executed the commands correctly. The output was redirected to files in /mnt/sdcard. Post those 3 *.txt files here.
chip17 said:
Other issue is with the microSD. The G tablet doesn't see it. I know the card is good my testing it in other devices. Recovery doesn't see it either. All I can access is the internal memory.
Click to expand...
Click to collapse
Actually, as the mount command output shows, both the internal SD card and the external one are recognized by the gTablet. The internal one is mounted at /mnt/sdcard and the external one at /mnt/emmc--which, BTW, is the exact opposite of the standard arrangement. Did you fiddle with the vold.fstab file to arrange it like it that or did you use the official method (Settings > CyanogenMod Settings > Tablet tweaks > switch Internal sdcard?
BTW, did you try my recommendations?:
rajeevvp said:
Try playing with the "USB debugging" and "USB debugging notify" settings in Settings > Applications > Development.
Click to expand...
Click to collapse
I'm trying to work past an issue so that I can use Adam's Ubuntu total wipe/restore. Right now it stalls on the first step of writing zeros to MLO. In this post Celtic was able to get past it using parted but I'm having trouble using the tool. When I run it in an ADB shell it tells me "Device not found" or something similar...Any suggestions?
Facts:
1) ADB is working fine. I can get a shell and browse the NT.
2) I'm unable to mount any partitions except these:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p1 on /sdcard type vfat
Thanks to Celtic, I've got this licked. It's running Adam's awesome Ubuntu recovery as I type
If anyone has trouble with this, do the following.
1) Copy parted out of snowball-mod\snowball-mod\nook-update-package.zip\nook-update-package\system-x\bin. Put it in a folder with ADB.
2) 'adb push parted /'
3) 'adb shell'
4) 'parted /dev/block/mmcblk0 print'
5) answer yes, fix, fix.
Moved To Q&A
Please post all questions in the Q&A section
thanks I will link this how-to to my FAQ
Sent from XDA premium using my Nook Tablet
[ info ]
so friends i know some of u are getting pissed because Sony didnt include MSC (mass storage mode) in the Xperia S/U/P GB firmware... the MTP mode is fine but some users (including me) prefer the MSC mode...
so here is a MOD/HACK which will enable that functionality!!!
[ credits ]
Napstar - for discussing this workaround which was ment for recovery but it works in OS very well
rogro82 - for creating and posting the GScript App here
finally me (DooMLoRD) - for implementing it for Xperia S/U/P and creating this easy to use package
[ requirements ]
stock GingerBread firmware
rooted device with busybox installed
[ downloads ]
APP for Xperia S
APP for Xperia U/P
if u want me to make a version of this app for ur Xperia P, Sola read this
OLD MANUAL WAY
test it out and let me know ur feedback!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENJOY!!
Saw requirements and rooted, almost cried
But very good work u guys! Finally someone made this mod! I'll test out when bl is unlocked! xD
Sent from my LT26i using xda premium
Awesome! Working perfectly for me. Thanks! Was hoping for something like this
Thank you very much DooMLoRD Now copying is speeeedy...even 28MB/s
Sweet!!
Code:
[260388.740074] usb 1-4: new high speed USB device using ehci_hcd and address 60
[260388.878673] usb 1-4: New USB device found, idVendor=0fce, idProduct=b169
[260388.878680] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[260388.878683] usb 1-4: Product: SEMC HSUSB Device
[260388.878686] usb 1-4: Manufacturer: SEMC
[260388.878688] usb 1-4: SerialNumber: **********
[260388.878919] usb 1-4: configuration #1 chosen from 1 choice
[260388.880622] scsi12 : SCSI emulation for USB Mass Storage devices
[260388.880894] usb-storage: device found at 60
[260388.880897] usb-storage: waiting for device to settle before scanning
[260393.876839] usb-storage: device scan complete
[260393.877392] scsi 12:0:0:0: Direct-Access SEMC Mass storage 0100 PQ: 0 ANSI: 4
[260393.878421] sd 12:0:0:0: Attached scsi generic sg2 type 0
[260393.880092] sd 12:0:0:0: [sdb] 54128640 512-byte logical blocks: (27.7 GB/25.8 GiB)
[260393.880585] sd 12:0:0:0: [sdb] Write Protect is off
[260393.880591] sd 12:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[260393.880596] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.882455] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.882463] sdb:
[260393.891209] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.891218] sd 12:0:0:0: [sdb] Attached SCSI removable disk
[260394.093218] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Brilliant! and so simple too, 2 lines! Makes the recent donation all the more sweet, so yet again - thanks DooMLoRD & Napstar
It seriously screws this Notification Bar mod, but that can go in favour of this
EDIT: also works on SO-02D - 6.0.A.4.1 (personal project I'm working on..)
wow i didn't think you would release it this quickly donation coming your way, thanks a lot man!
Incredible!
Thanks you for all your work, donation is coming
I dunno why Sony has removed this function in the rom, MTP is horrible!
One more great job doom.
Thx you for developing for SXS.
Cant wait to put my hands on it.
Sent from my LT26i using XDA
some funny things I did (don't try this at home)
I've formatted the mounted internal SDCard as NTFS and guess what, it didn't mount properly (as expected) by the operating system - but using gscript, it did mount properly in windows.
After that, I used adb shell to gain access to the device to manually mount /dev/block/mmcblk0p15 and voila, it supports NTFS - though root explorer etc. It's not practical (as the OS reports the /sdcard/ is not mounted - even though it is), but still fun to investigate.
Code:
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 348.4M 64.0K 348.3M 0% /dev
tmpfs 348.4M 0 348.4M 0% /mnt/asec
tmpfs 348.4M 0 348.4M 0% /mnt/obb
/dev/block/mmcblk0p12
1007.9M 352.9M 654.9M 35% /system
/dev/block/mmcblk0p14
2.0G 484.3M 1.5G 24% /data
/dev/block/mmcblk0p13
246.1M 164.0M 82.0M 67% /cache
/dev/block/mmcblk0p10
7.9M 4.1M 3.7M 53% /data/idd
/dev/block/mmcblk0p13
246.1M 164.0M 82.0M 67% /data/dalvik-cache
/dev/block/mmcblk0p15
25.8G 86.5M 25.7G 0% /mnt/sdcard
# mount
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p14 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data/idd type ext4 (rw,nosuid,nodev,relatime,barrier=0,data=ordered)
/dev/block/mmcblk0p13 on /data/dalvik-cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /mnt/sdcard type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_
multiplier=1)
---------- Post added at 05:11 PM ---------- Previous post was at 04:54 PM ----------
On the side note - which part denotes how the system boots up and mounts /sdcard/ ? I am not that good with android in terms of bootup sequences, so I thought I can look up /etc/fstab but there's nothing there
^ /etc/vold.fstab
possibly
the dir and symlinks are done in init
Sent from my LT26i using XDA
works perfectly
but i was just wondering (not complaining)
would it be possible to make this part of the os so you dont have to run the script
so for example, mod a system file?
Works here...Ubuntu 12.04 64bit...
Thx
It's even better than Xperia Arc. I've simultanously Mass Storage mode, MTP mode and access in phone.
..i just donated 10$ for good cofee or something you like Best regards
Seems great work. It is possible to install Gscript zip file manually by using root explorer and then follow rest of the guideline ?
Autmatic Mounting and Unmounting
Hello,
I hate MTP so much that I cried tears of joy after seeing this post, so thx Doomlord!
The only thing annoying was always having to manually Mount / Dismount.
So I went and made a Tasker Profile that complete automates this
You need the following for this to work:
Tasker
Autoshortcut
Locale Power Source Plug-In
Step 1:
Follow Doomlords awesome instructions on page 1
Step 2:
Install all of the above mentioned Programs
Step 3:
Download the attached ZIP File and extract to /sdcard/Tasker/profiles
Step 4:
Import the profiles by long pressing the "Profiles" Button in Tasker (top left) and then pressing import. And don't forget to engable the profile.
Step 5:
Now everytime you connect to USB the drive gets mounted, everytime you disconnect it gets dismounted.
It should work with Locale instead of Tasker, too but I don't own that programm so I haven't tried.
Enjoy
Just remembered we had http://forum.xda-developers.com/showthread.php?t=1389375 on the Desire/N1 before we fixed UMS properly. Works the same way, just need to change the LUN file path.
Sent from my LT26i using XDA
OLD INFO!
[ info ]
so friends i know some of u are getting pissed because Sony didnt include MSC (mass storage mode) in the Xperia S GB firmware... the MTP mode is fine but some users (including me) prefer the MSC mode...
so here is a MOD/HACK which will enable that functionality!!!
[ credits ]
Napstar - for discussing this workaround which was ment for recovery but it works in OS very well
rogro82 - for creating and posting the GScript App here
finally me (DooMLoRD) - for implementing it for Xperia S and creating this easy to use package
[ requirements ]
stock GingerBread firmware (.62/.63/.73)
rooted device
recovery
[ how to install? ]
download the zip file provided in download section below
put the zip on sdcard
reboot into recovery
flash the zip from sdcard
reboot into system
open app drawer, a new app GScript will be available
open GScript app and click MENU button
select "Add Script"
now select "sdcard-mount.sh"
now click on "Save"
do the above 4 steps again to add "sdcard-unmount.sh"
now go to homescreen and long press on blank space, you will get a menu to add things to homescreen
now select "Shortcuts" and browse to "GScript Lite"
now select "sdcard-mount"
a shortcut will now be placed on homescreen to autolaunch this script
do the above 3 steps to add "sdcard-unmount"
that it!! now everything is in place!
[ how to use? ]
mounting
now when ever u have the phone connected to PC just click on the shortcut "sdcard-mount" (you might get a SuperUser prompt, accept/allow it)
at first run it might take a while for the new drive to show up as drivers are getting installed in background but once thats done sdcard should now be mounted to PC
unmounting
now to unmount, safely remove the drive from ur PC and click on shortcut "sdcard-unmount"
done sdcard is now unmounted!!!
[ downloads ]
KINDLY DO NOT MIRROR MY FILES
SDCARD Mounter as MSC Mode (V01)
test it out and let me know ur feedback!!!
ENJOY!!
DooMLoRD said:
i hope u mean "I hate MTP so much...."
Click to expand...
Click to collapse
Haha, edited
What to you think of the script, any other way to automate it?
Mycorrhiza said:
Haha, edited
What to you think of the script, any other way to automate it?
Click to expand...
Click to collapse
i personally dont want to automate it as i keep connecting to PC often but dont want the sdcard mounted all the time...
Mycorrhiza said:
Haha, edited
What to you think of the script, any other way to automate it?
Click to expand...
Click to collapse
There's an app for that I posted just before you. I'll fix it to make it work on the XPS later today
Sent from my LT26i using XDA
Using a usb key for a live USB of remix os in the same time as a data external drive isn't possible actually due to windows not being able to see further than one partition on the stick (ok, except if we use remix os partition as the data one ... without accidentally messing it up, but looks like it has an automatic size and the place it uses limit us).
I remember I had a similar problem with one of my first Linux live too. Not sure how I dealt with it but I were able to end having both after some search and understanding : liveOS partition, and a data partition visible on Windows (no problem like this with a Linux).
I'll try to reproduce with a linux if I have the time but here is what I'm looking for :
Ooops, since I can't post links nor upload images, I put the image link as my twitter in my profile
So, won't the data partition be ok to use on windows if like on 2nd example, the live os isn't installed in the same place as in the 1rst one ? I already tried to prepare 2 partitions before using the installation tool and choose the one destined for remixOS (and only visible) to install on it but the tool always end wiping ALL the key, and then partitioning appears to be the same.
Can pass through this problem be done by the tool ? (being able to install NEXT to a data partition to keep it visible by windows, or hide remixOS ones)
I ideally need this key for both usages, and if it's possible I think I'm not alone.
Does this can be added ?
@Esdeve
The reason you don't see the partitions in Windows is because they are in EXT4 filesystem, but I guess u know that already .
There are few software solutions for mounting these, but it will only mount the whole Remix system partiton, not the "partition inside the partition".
So basically it'll mount the partition with data.img (remix data partition), inird, ramdisk.... But not the data.img itself.
I don't think it's possible too easily and quickly make this automatic. Even on Linux u'd have to set up data.img to be automatically mounted when pendrive is detected.
Using the official .iso to USB installer won't allow you do what you need, but you can boot Linux on ur PC and with gParted extend/shrink existing USB partitions and maybe make a new one for other purposes.
Sent from mobile
Yup. Know that. I think you didn't understood what I'm looking to do ... but I may express poorly in english when speaking about computing subjects. Or I may not understand myself what you are answering too ^^'
Here we re-go : I'm looking to have both a data partition and the two partitions of RemixOS which are a Fat32 and an Ext one. I don't need having an access to the Ext, and I don't want to use the Fat32 one as a data partition because it's the OS partition, it's unsafe to use it for this, I may mess with it accidentally.
I don't need to modify the sizes of any partitions (from a Linux or not) since installation leaves room to be used. But since the fat32 already exists, I basically can't create/keep a 2nd fat/fat32/NTFS one next to it, this is no use, windows won't see it, the fat32 from remixOS is first, so Windows only sees this one and not my own, and I can't change that with the way the installation is made. Moving the two RemixOS partitions is of course totally excluded and will render the os unable to boot so I won't try it except maybe if able to do #3.
Solutions ?
1 - Being able to do what I just proposed in 1rst post : have the devs make the installer able to install in place of a designated partition (and not on all the key), in the right part of what is displayed in he graphic from my partition software, leaving the possibility to create afterward a fat/fat32/ntfs partition to the left, and seen by windows instead of the remixOS's fat32 without destroying the boot ... Uh, if that does the trick, I didn't experiment this sort of things a lot but I'm sure I succeeded with a live persistent linux once.
2 - RemixOS installer may only use EXT partitions and no fat32 ? Can't it ? Leaving windows readable formats free to use for something else.
3 - I'm planing to move the partitions like needed (there I know I'll be able to access my personal data partition I created), and then try some Grub thing on my key to keep the live system bootable, but I'm not sure to remember how to, nor if this will work, nor even if grub can launch RemixOS.
Well. I'd add to all this that I'm not specially searching for help, I know actually except for the complex solution #3, that it's impossible to manage what I need. It's more like an asking/proposing of feature/possibility. And I'm pretty sure I won't be the only one to think it's waste to use my 3.0 stick rendering it unable to serve in the same time for portable data storage when it always have loooots of place.
I read in the ask/propose feature part of the devs site to come post her ... So I did. But there is no "evolution" section and only a device classifying here. So here I wrote. Sorry if misunderstood.
The problem with what you wrote is that you overcomplicate it. Keep it simple and short - that's best.
Did understood correctly that you want to use the USB as Remix Live Stick and as a typical storage device?
Did you read my whole post?
Remix when installed on USB should use all it's space - makes 3 partitions:
1. Boot
2. System
3. Data for external storage purposes.
The 3rd is what you see in Windows.
All you need to do now is just to adjust sizes of other partitions (it's possible without corrupting existing files), but hard to do under Windows. Then u need to expand this 3rd partition.
Sent from mobile
Sorry ^^' I know I use too much words, but it appears I can't make simple when speaking about technical matters, and in a language I'm not used to resume tech things.
Of course, I read your posts. I"m on a 32gb stick. I can see 3 partitions :
1 : REMIX_OS (apparently data, since it's the only one I can access from windows). Fat32. 7.64Gb sized.
2 : REMIXOSSYS. Fat32 too. But not accessible from windows (I understand this like it's because it's 2nd principal partition, so windumbOS doesn't see it). 5Gb sized. Part of the system. including the boot isn't it ?
3 : Third partition. System. Format unknown from Windows or either with Linux (using gParted). Named "unknown". And takes full remnants of the stick capacity (16Gb). Does it needs theses 16Gb from the start ? Apparently not obligatory since looking at the space used from the live OS, seems doesn't uses it a lot compared to the available place.
This last one is the main problem for me. I don't see how to treat this "other" partition, and at start, then reading your 1/2/3 list, I believed that was this one used as "data". I understand well there are ext partitions within since the os is an unix, but I don't see the whole as an EXT partition, whenever I'm on Windows or Linux, so with my knowledge and capacities, I can't access nor reduce it.
Will try command line or to find a similar problem with solution, but I think this won't change lot here. About the two Fat32, I'm not really confident about what you said and the possibility of moving the whole, and especially theses two. Systems and boots don't like this, they don't find each others well afterward ^^ don't they ? Resizing the two first without moving ? Ok. But that will just make me room for two new small useless partitions between the three others, and I strongly believe windows won't see em but only the "REMIX_OS" one.
If possible, I'm going to try another way to obtain live remixOS usb too. Can't unetbootin or such do the job ?
If the choice of having data at the beginning isn't technical, can't the devs make the installation create the data partition at the end instead, plus add an option advising a minimal space for the "unknown" partition and letting users chose what size it will be ?
Esdeve said:
Sorry ^^' I know I use too much words, but it appears I can't make simple when speaking about technical matters, and in a language I'm not used to resume tech things.
Of course, I read your posts. I"m on a 32gb stick. I can see 3 partitions :
1 : REMIX_OS (apparently data, since it's the only one I can access from windows). Fat32. 7.64Gb sized.
2 : REMIXOSSYS. Fat32 too. But not accessible from windows (I understand this like it's because it's 2nd principal partition, so windumbOS doesn't see it). 5Gb sized. Part of the system. including the boot isn't it ?
3 : Third partition. System. Format unknown from Windows or either with Linux (using gParted). Named "unknown". And takes full remnants of the stick capacity (16Gb). Does it needs theses 16Gb from the start ? Apparently not obligatory since looking at the space used from the live OS, seems doesn't uses it a lot compared to the available place.
This last one is the main problem for me. I don't see how to treat this "other" partition, and at start, then reading your 1/2/3 list, I believed that was this one used as "data". I understand well there are ext partitions within since the os is an unix, but I don't see the whole as an EXT partition, whenever I'm on Windows or Linux, so with my knowledge and capacities, I can't access nor reduce it.
Will try command line or to find a similar problem with solution, but I think this won't change lot here. About the two Fat32, I'm not really confident about what you said and the possibility of moving the whole, and especially theses two. Systems and boots don't like this, they don't find each others well afterward ^^ don't they ? Resizing the two first without moving ? Ok. But that will just make me room for two new small useless partitions between the three others, and I strongly believe windows won't see em but only the "REMIX_OS" one.
If possible, I'm going to try another way to obtain live remixOS usb too. Can't unetbootin or such do the job ?
If the choice isn't technical, can't the devs make the installation create the data partition at the end instead of the beginning, plus add an option advising a minimal space for the "unknown" partition and letting users chose what size it will be ?
Click to expand...
Click to collapse
The unknown should be ext4 userdata mounted as /data and RemixOSSys should only contain system
Can you post a screenshot of the contents of Remix_OS and within RemixOS check mount and df to check what's mounted where.
About the two command lines from within remixOS. I don't know how to copy it or save it to a file. Looks like shortcuts/commands I'm used to aren't suited here (tried to use "script" and "-l > /path/to/file.txt". Either end up with a file protected in writing, or path not existing, maybe even command not existing answers). So how do I do that ? Or maybe where will I be enabled to create a .txt from the terminal ?
Esdeve said:
About the two command lines from within remixOS. I don't know how to copy it or save it to a file. Looks like shortcuts/commands I'm used to aren't suited here (tried to use "script" and "-l > /path/to/file.txt". Either end up with a file protected in writing, or path not existing, maybe even command not existing answers). So how do I do that ? Or maybe where will I be enabled to create a .txt from the terminal ?
Click to expand...
Click to collapse
You should be able to redirect to sdcard:
mount > /sdcard/mount.txt
df >> /sdcard/mount.txt
Hmm..
If you don't wish Windows to have access to your usb stick...
Use "diskmanager" and remove the drive letter
Cheers
@mitchell4you : That's not what I propose.
@HypoTurtle, and to recapitulate for anyone about screenshots :
Since I can't post links for the moment, I put the screens links in my profile in place of contact infos. I'll modify my posts later when I'll own the rights.
Twitter is for the first post of the thread.
G+ is the Remix_OS partition screen you asked for.
Say if other partition screenshot is needed.
Next are the command lines ...
Mount :
tmpfs on / type tmpfs (ro,relatime)
/dev/loop1 on /system type ext4 (ro,relatime,data=ordered)
/dev/block/sdb3 on /data type ext4 (rw,noatime,nodiratime,data=ordered)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime,mode=755)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,relatime,mode=750,gid=1000)
tmpfs on /mnt type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,relatime)
none on /cache type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_1 on /mnt/media_rw/E45C9A015C99CF24 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/E45C9A015C99CF24 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_2 on /mnt/media_rw/01D0A77D0C4455E0 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/01D0A77D0C4455E0 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_3 on /mnt/media_rw/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type ext4 (rw,dirsync,nosuid,nodev,noatime,data=ordered)
/dev/fuse on /mnt/runtime/default/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_5 on /mnt/media_rw/7326C07B75B67850 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/7326C07B75B67850 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_7 on /mnt/media_rw/288A9EF38A9EBCAE type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/288A9EF38A9EBCAE type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_8 on /mnt/media_rw/01D0A77D072BDC90 type fuseblk (rw,dirsync,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/fuse on /mnt/runtime/default/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/01D0A77D072BDC90 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_17 on /mnt/media_rw/3834-74A4 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/3834-74A4 type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:8_18 on /mnt/media_rw/C004-4EFA type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/C004-4EFA type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
And df :
Filesystem-----------------------------1K-blocks-----Used-------Available-----Use%----Mounted on
tmpfs--------------------------------4012216--------3304-------4008912-------1%--------/
/dev/loop1--------------------------2539312-------1962424----576888-------78%------/system
/dev/block/sdb3------------------16382888-----1212340-----15170548------8%-------/data
tmpfs--------------------------------4012216--------76-----------4012140-------1%--------/dev
none---------------------------------4012216--------12------------4012204------1%--------/sys/fs/cgroup
tmpfs--------------------------------4012216--------0-------------4012216------0%-------/mnt
none---------------------------------4012216--------0-------------4012216------0%-------/cache
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/default/emulated
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/read/emulated
/dev/fuse---------------------------16382888------1212340-----15170548----8%-------/mnt/runtime/write/emulated
/dev/block/vold/public:8_1----102396---------28804-------73592--------29%-----/mnt/media_rw/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/default/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/read/E45C9A015C99CF24
/dev/fuse---------------------------102396---------28804-------73592--------29%-----/mnt/runtime/write/E45C9A015C99CF24
/dev/block/vold/public:8_2----297780836----115267204--182513632---39%----/mnt/media_rw/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/default/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/read/01D0A77D0C4455E0
/dev/fuse----------------------------297780836---115267204---182513632---39%---/mnt/runtime/write/01D0A77D0C4455E0
/dev/block/vold/public:8_3-----92798268----4900736-----87897532---6%----/mnt/media_rw/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------92798268----4900736-----87897532---6%----/mnt/runtime/default/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------927982686---4900736----87897532---6%----/mnt/runtime/read/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/fuse-----------------------------92798268-----4900736----87897532---6%----/mnt/runtime/write/720ddd36-a9a5-4e8d-a80f-bf25799d1fc7
/dev/block/vold/public:8_5-----12584956------256216------12328740----3%---/mnt/media_rw/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/default/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/read/7326C07B75B67850
/dev/fuse-----------------------------12584956-----256216-------12328740----3%--/mnt/runtime/write/7326C07B75B67850
/dev/block/vold/public:8_7------94412796-----61516412-----32896384--66%-/mnt/media_rw/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/default/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/read/288A9EF38A9EBCAE
/dev/fuse-----------------------------94412796-----61516412-----32896384---66%-/mnt/runtime/write/288A9EF38A9EBCAE
/dev/block/vold/public:8_8------220676840---183026824--37650016---83%--/mnt/media_rw/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/default/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/read/01D0A77D072BDC90
/dev/fuse-----------------------------220676840---183026824---37650016---83%--/mnt/runtime/write/01D0A77D072BDC90
/dev/block/vold/public:8_17-----7993744------68-------------7993676----1%----/mnt/media_rw/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/default/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/read/3834-74A4
/dev/fuse-----------------------------7993744------68-------------7993676-----1%---/mnt/runtime/write/3834-74A4
/dev/block/vold/public:8_18----5230592-------1178680------4051912-----23%--/mnt/media_rw/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680------4051912-----23%--/mnt/runtime/default/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680------4051912-----23%--/mnt/runtime/read/C004-4EFA
/dev/fuse-----------------------------5230592-------1178680---4051912--------23%--/mnt/runtime/write/C004-4EFA
Hi. Everyone knows that FB app saves its downloaded images in DCIM folder. At the same time, Google Photo doesn't allow to select subfolders elegible to media auto-backup. So my idea is to create a symbolic link between that Facebook subfolder and another one on different location, and so properly save photos and videos on a different folder.
There's any way to do it? I found different procedures on different site but nothing seems to work (btw, i don't know is a procedure fault or an android 10 fault), naturally using Magisk root permissions.
peppe1996 said:
Hi. Everyone knows that FB app saves its downloaded images in DCIM folder. At the same time, Google Photo doesn't allow to select subfolders elegible to media auto-backup. So my idea is to create a symbolic link between that Facebook subfolder and another one on different location, and so properly save photos and videos on a different folder.
There's any way to do it? I found different procedures on different site but nothing seems to work (btw, i don't know is a procedure fault or an android 10 fault), naturally using Magisk root permissions.
Click to expand...
Click to collapse
When you download a photo from within the Facebook app, it is stored in DCIM/Facebook. When you launch the Gallery app, the image shows up right under "Photos". Also in the gallery app if you click on the "COLLECTIONS" tab, it shows up there under "Camera".
FYI: Creating a symlink basically doesn't require Android is got rooted, unless you want to create symlinks in Android's /system partition.
I think it's really easy to create symlinks on Android.
Example:
Code:
adb devices
adb shell "mkdir -p /data/DCIM-Facebook 2>/dev/null"
adb shell "cp -a /DCIM/Facebook /data/DCIM-Facebook"
adb shell "rm -rf /DCIM/Facebook"
adb shell "ln -sf /data/DCIM-Facebook /DCIM/Facebook"
adb shell "ls -l /DCIM/Facebook"
jwoegerbauer said:
When you download a photo from within the Facebook app, it is stored in DCIM/Facebook. When you launch the Gallery app, the image shows up right under "Photos". Also in the gallery app if you click on the "COLLECTIONS" tab, it shows up there under "Camera".
FYI: Creating a symlink basically doesn't require Android is got rooted, unless you want to create symlinks in Android's /system partition.
I think it's really easy to create symlinks on Android.
Example:
Code:
adb devices
adb shell "mkdir -p /data/DCIM-Facebook 2>/dev/null"
adb shell "cp -a /DCIM/Facebook /data/DCIM-Facebook"
adb shell "rm -rf /DCIM/Facebook"
adb shell "ln -sf /data/DCIM-Facebook /DCIM/Facebook"
adb shell "ls -l /DCIM/Facebook"
Click to expand...
Click to collapse
Thanks for the answer man. I tried your procedure and this is what happened https://ibb.co/py7mkfK
This is the classic error that i had with other procedures.
@peppe1996
My fault was to NOT tell you that symlinks only are possible on partitions that support it, means their filesystem is either ext2 or ext3 or ext4 or yaffs2.
Internal sdcard /storage/emulated/0 where folder DCIM resides has filesystem /dev/fuse. Hence my script example was totally wrong.
Sorry for this.
jwoegerbauer said:
@peppe1996
My fault was to NOT tell you that symlinks only are possible on partitions that support it, means their filesystem is either ext2 or ext3 or ext4 or yaffs2.
Internal sdcard /storage/emulated/0 where folder DCIM resides has filesystem /dev/fuse. Hence my script example was totally wrong.
Sorry for this.
Click to expand...
Click to collapse
NP man. So can I do nothing about?
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
jwoegerbauer said:
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
Click to expand...
Click to collapse
Thanks mate for tips, but i think this is not i need for my scope. If I'll have the same file tree in both path, Facebook images must remain in the original folder and Google Photo will upload them. If i can preserve some file to be binded, I could try to insert a .nomedia file in DCIM/Facebook. So, DCIM/Facebook will be hidden to Google Photo and i can continue to see Facebook downloaded images in Pictures folder (on the contrary, also .nomedia will be copied and also Pictures/Facebook will be not visible on Google Photo).
@peppe1996
IMHO an alternative is to create a so-called bind mount. A bind mount is an alternate view of a directory tree. Classically, mounting creates a view of a storage device as a directory tree. A bind mount instead takes an existing directory tree and replicates it under a different point. The directories and files in the bind mount are the same as the original. Any modification on one side is immediately reflected on the other side, since the two views show the same data.
Example pseudo code:
Code:
mount -o bind /some/where /else/where
In your case this should problemfree work because both /sdcard/DCIM/Facebook and /sdcard/Pictures have the same filesystem.
FYI: mount command by default is available in any Android version.
IMPORTANT: Such a bind mount isn't persistent: you have to get it created everytime when Android boots up. That in turn requires to have an init.d script what does the job.
Click to expand...
Click to collapse
Hello, i just bring this here up again because i have a similar problem.
I tryed your command and it passed without errors. But without the wished effect.
Code:
:/ # mount -o bind /storage/231A-1B1B/DCIM /storage/emulated/0/DCIM
This is the output of "mount"
Code:
:/ # mount <
rootfs on / type rootfs (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=891960k,nr_inodes=163101,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
none on /dev/memcg type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
none on /dev/cpuctl type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
none on /dev/bfqio type cgroup (rw,relatime,bfqio)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/dev/block/vold/public:179,65 on /mnt/media_rw/9FE1-FB0F type exfat (rw,dirsync,nosuid,nodev,noexec,noatime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,symlink=0,bps=512,errors=remount-ro)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
/dev/block/mmcblk0p23 on /system type ext4 (ro,seclabel,relatime,discard)
none on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
none on /config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/block/mmcblk0p24 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p25 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=891960k,nr_inodes=163101,mode=755)
/sbin/.magisk/block/cache on /sbin/.magisk/mirror/cache type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,discard)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
/sbin/.magisk/block/data on /sbin/.magisk/modules type ext4 (rw,seclabel,relatime,noauto_da_alloc,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
tmpfs on /storage/self type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=891960k,nr_inodes=163101,mode=755,gid=1000)
/dev/block/vold/public:179,97 on /mnt/media_rw/231A-1B1B type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/mnt/media_rw/231A-1B1B on /mnt/runtime/default/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/231A-1B1B on /mnt/runtime/read/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /mnt/runtime/write/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /storage/231A-1B1B type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/231A-1B1B on /storage/emulated/0/DCIM type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
The last line appears after i try to mount the folder. Does anybody k ow what goes wrong here?
Marco