Ok, I have a FreeNAS server setup at home and I have SSH enabled. Anyways, i'm fine and succeded in connection via SSH connectbot and having portforward of 139 to a local of 8888
This works FINE with ES file manager or even Astro file manager, I can browse my FreeNas server. Problems are though:
1. Why can't I actively view images or videos(not that I want to so much through 3G) when I click on the image, and it won't load up? This happens the same way if I do a local browsing via SMB on astro file manager on my LAN at home.
What works: When I do a CIFS mount using that app someone made here, the CIFS manager or whatever, I can stream videos, images whatever fine.
Now if I can get that to work via the ssh tunnel. I tried creating a CIFS via the ssh tunnel but somehow it doesn't work and I get error like "segmentation fault" with mount.
Anyone have any idea? I can transfer files file but I want to have option to quickly view pictures on my server rather than copy the paste then open up.
Ok update, I can do a mount CIFS manually in terminal, but the CIFS module app still doesn't work...
I guess SMB shares won't allow streaming either way?
When you use a file manager to browse files on your NAS box over SSH (or FTP), the remote files are not mapped to a local path. As a consequence, you can only browse these files with applications able to use CIFS, SSH or FTP connections. Your gallery apps and media players can't access these files directly because, unlike EStrong of ASTRO, they have no CIFS/SSH/FTP client built in.
When you mount a CIFS share on your NAS box using CifsManager, all the files within that share will be mapped to a "local" file. The Android system will know that when you acces /mnt/cifs/MyShare/peanut.png, it is in fact the file peanut.png on your network share. The gallery or media player apps access a local file and aren't aware of the fact that the Android system actually accesses a file on your NAS box instead.
I have no idea why you can't mount a cifs share over your SSH port forwarding.
A segmentation fault has to do with memory access.. and that doesn't make any sense. It might be caused by the fact that port 137-139 are NETBIOS ports. Win2K and higher use 445 for CIFS instead. You might want to try forwarding port 137 (TCP/UDP) and 138 (UDP) too.. or forwarding port 445 (TCP/UDP) instead. Then again.. it might be something else entirely.
If this doesn't work, maybe you can try with some type of VPN instead of SSH port forwarding?
Actually figured it out.. hope this post will help others with similar issues.
Problem is the mount on android is a bit finicky when apply options, it's a certain order or some sort. I got it working by using the '-o' by putting port=xxxx,ip=xx.xx.xx.xx
It was segmenting for who knows what when I put ip,port. I guess order matters on android vs the linux mount command. Strange indeed
Works now, though my vids are wrong res when streaming, who knows why but not that I care too much lol.
Works okay now, but pretty much 2 step process to access files at home which is a pain. I guess I can buy the andftp client to do a quick file transfer access.
I am trying to download to my samba share through xbmctorrent plugin but i get an error that it cannot download to unmounted share.
is there any way of mounting the sambashare in the ftv system so it will see it as an internal folder or something ?
I am also looking to do the same thing for retroarch. The 8GB internal storge aint big enough for all the roms
quacka said:
I am also looking to do the same thing for retroarch. The 8GB internal storge aint big enough for all the roms
Click to expand...
Click to collapse
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805
rooted
gujju said:
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805
Click to expand...
Click to collapse
yes i have rooted it and yes i see it in xbmc. the problem is with xbmctorrent plugin that cannot download to an unmounted share drive.
gujju said:
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805
Click to expand...
Click to collapse
Think this is missing the point, the issue is attempting to mount network shares as native paths, not within another app. The link provided only discusses USB drives, not network.
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
Thanks hmagoo, that worked for me finally.
I think I was trying it via SSH hence never got it to work.
How do I make the share remain after a power cycle?
hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
Please make a guide
If using this code using ADB allows us to mount network drives a little more elaboration needs to be done..
Vylle said:
Please make a guide
If using this code using ADB allows us to mount network drives a little more elaboration needs to be done..
Click to expand...
Click to collapse
I only tried using samba shares because I wanted to launch MXPlayer as an external player to play xvid files through xbmc, but I found it was easier to just disable libstagefright and mediacodec in xbmc settings and the xvid files play smoothly.
if you used an app like Script Manager you should be able to run a script upon boot-up that makes the directory and mounts the share.
hmagoo said:
I only tried using samba shares because I wanted to launch MXPlayer as an external player to play xvid files through xbmc, but I found it was easier to just disable libstagefright and mediacodec in xbmc settings and the xvid files play smoothly.
if you used an app like Script Manager you should be able to run a script upon boot-up that makes the directory and mounts the share.
Click to expand...
Click to collapse
I have installed tasker. I set the command to run on boot as Shell Script but it doesn't seem to work. it seem only to work when running via adb shell for me. No idea what I am doing wrong
I have to apply the script after every reboot also. Has anyone found a way to keep it after boot?
hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
dont want to get too off topic but what if you are using NFS. since that doesnt require a username and password what would the command look like?
mejdam said:
dont want to get too off topic but what if you are using NFS. since that doesnt require a username and password what would the command look like?
Click to expand...
Click to collapse
same sort of thing
mount /mnt/obb/nas 192.168.1.23:/path/to/share
adionita said:
I have to apply the script after every reboot also. Has anyone found a way to keep it after boot?
Click to expand...
Click to collapse
Sorry to bump this old thread but I'm also in the need of this,
Have you figured out a way of auto remounting the share???
Hi could you clever folks help a guy out, I'm trying to do what it says in the thread title but I do not have a PC, I use agk fire and es file explorer.
can anyone do a quick idiots guide on how I can do this.
Many thanks.
Just go to you SPMC foldr and delete the thumbnail folder, and make sure you also delete the texture database file too. The thumbnail folder will auto recreate itself. If you do not delete the textures DB file iit will take a long time for Kodi to make new thumbnails.
porkenhimer said:
Just go to you SPMC foldr and delete the thumbnail folder, and make sure you also delete the texture database file too. The thumbnail folder will auto recreate itself. If you do not delete the textures DB file iit will take a long time for Kodi to make new thumbnails.
Click to expand...
Click to collapse
Thanks for the reply.
Yes I already know how to delete thumbs and textures 13.dB.
I'm trying to redirect thumbs to external flash drive. It can be done but I have no PC.
Think this is for kodi
from ftv news
how can I do this manually using esfile explorer for spmc
Guide
Ensure that your USB drive is connected to your Fire TV, that Kodi is installed on your Fire TV, and that you’ve launched Kodi at least once before proceeding with this guide. It does not matter if Kodi is installed on the Fire TV’s internal storage or on external USB storage.
Force stop Kodi on your Fire TV by going to Settings > Applications > Manage Installed Applications, selecting Kodi, and selecting the Force stop option.
Connect to your Fire TV via ADB.
Open a Fire TV shell prompt by running the command:
adb shell
Create a directory called kodi on your USB drive where we will move Kodi’s thumbnail files by running the command:
mkdir /storage/extUsb/kodi
Copy Kodi’s thumbnail files to your USB drive by running the command:
cp -r /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/Thumbnails /storage/extUsb/kodi/
This may take a while depending on the size of your Kodi installation and the speed of your USB drive.
Create a blank Kodi configuration file by running the command:
touch /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml
Fill the configuration file by running the command:
echo \<advancedsettings\>\<pathsubstitution\>\<substitute\>\<from\>special://thumbnails/\</from\>\<to\>/storage/extUsb/kodi/Thumbnails/\</to\>\</substitute\>\</pathsubstitution\>\</advancedsettings\> > /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml
Launch Kodi and verify everything is working correctly.
Delete Kodi’s thumbnail files from your Fire TV’s internal storage by running the command:
rm -rf /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/Thumbnails
Can anyone please help
astro77 said:
Hi could you clever folks help a guy out, I'm trying to do what it says in the thread title but I do not have a PC, I use agk fire and es file explorer.
can anyone do a quick idiots guide on how I can do this.
Many thanks.
Click to expand...
Click to collapse
I have a Mac and a PC and I've never tried but unless someone corrects me....android terminal is very similar to Mac as it applies to Unix. So you can install android terminal on your device and run the same commands in the aftvnews guide. I'm not even 50% certain it works. Your android might need to be rooted but not certain there either.
Its just I noticed your notngetting many answers. At the very least I'm sure itnwont hurtnto try. And, I'm very curious to see if it would work.
As I understand it there are definite limits, thats why the guides usually say Mac, PC or linux. But we can connect with adb (actually that's much simpler to do with android) so its might be worth a shot.
You will need to Google if you don't know manually copy and paste paths but this isnpretty simple too. Hope it works. And if someone knows of a reason this won't work hopefully you'll let both of us know.
Thank you a lot
Downloaded the terminal on my android tablet but have no idea how to connect to fire TV over WiFi using the terminal app.
Was going to just create a "text" XML file containing the correct path then just put it in the right location on my fire TV with esfile explorer and maybe copy a few folders from spmc to flash drive........
I'm sure its simple when you know how lol.
If that works for you that's even simpler. You can still use the terminal to adb push your XML. Place it in userdata. Then you'll probably need to delete textures13db from the database and restart kodi. Before the new updates this was how I stored thumbs and it worked as well as it does now. Once you verify advanced settings and it works you can delete the thumbnails from your internal sdcard.
Good stuff :good:
just don't know what to name the XML and the contents path for spmc.
As you can tell I'm not very experienced at this stuff.
edit:
something like
<advancedsettings\>\<pathsubstitution\>\<substitu te\>\<from\>special://thumbnails/\</from\>\<to\>/storage/extUsb/kodi/Thumbnails/\</to\>\</substitute\>\</pathsubstitution\>\</advancedsettings\>
please someone help
if you have done this by whatever method could you please open up your advanced XML file and copy and paste it here please.
Cracked it
made a text file using esfile explorer on my tablet named:
advancedsettings.xml
then put this in the file:
<advancedsettings>
<pathsubstitution>
<substitute>
<from>special://profile/Thumbnails/</from>
<to>/storage/extUsb/Thumbnails/</to>
</substitute>
</pathsubstitution>
connected my tablet to aftv using esfile explorer over WiFi and moved the file to spmc userdata
opened spmc and deleted textures and thumbs folder, close spmc, restarted and it worked.
thanks too all that replied
It's my first relevant post in here so please be benevolent and friendly to me .
Hello everyone,
After long hours of roaming around on the internet, Moto forums, PowerAMP forums (you wouldn't believe how many people posted this problem in there), huge exchange of emails and debugs to the Nexus Media Importer dev, and checking out many many topics here on XDA, I finally came across the only way to use an USB-OTG pendrive as a music library, and having Android detect it (through the Media Service) and build the music library for other media apps to use.
tl dr; Problem: You wanted loads of music without wasting precious internal memory. You tried using an USB pen but no mp3 apps were able to find the files, nor stickmount, nor whatever.
This is so far the only way to do this on android Marshmallow.
Believe me, I've tried almost everything one can do, including using the Nexus Media Importer, Stickmount, OTG Helper, etc (spoiler alert, none of these worked).
Why is this happening, you ask? Well, Google changed things on Android 6.x.x so much regarding filesystems and USB support that full read/write on USB OTG with other apps no longer works, although I've never tested on previous versions of Android. But I finally managed to find a way to do it, and here I intend to share it with you guys.
Requirements - Rooted phone and permissive SELinux (what is that and how do I do it? don't worry, it's easy and I'll explain a bit later)
1st step - Verify that your phone is capable of using USB-OTG. If it is not, check on play store for other apps that supposedly can enable USB Host support on your phone, although I've never tried them because I never needed, so I can't say anything. My phone is a Moto X 2014 and it comes with OTG support embedded.
2nd step - Format your pendrive as NTFS. This is very important because...
If you use your pendrive as Fat32, Android will mount it to a folder in /data/media_rw/blablabla with GID and UID 1023 (media_rw), which most apps don't have permissions to access, thus they won't be able to find your pendrive and build a music library. Why? Well, glad you asked...
...Since Fat32 doesn't support the linux permissions system, Android mounts the pendrive with the FUSE fs wrapper, which cloaks a permission system hard-coded into some file in the Android system that I wasn't able to tell how could I modify it in order to set the pen permissions as 777 root root.
You can do so by plugging your pen on a Windows PC and right clicking -> Format. Remember to backup your data, otherwise you will lose everything. Your pen will still be able to be used on Windows pcs and Macs. You could also use other fileformats...
... like EXT4 or f2fs or exFAT or whatever, but do it at your own risk. I have no idea if those would work, despite them being able to use the linux permission system.
3rd step - Install the wonderful app Paragon HFS and NTFS mounter from appstore or whatever. They say it isn't compatible with marshmallow but it is, the only issue is that it can't mount a pendrive automatically but it's very easy to do it manually. In the settings menu, you can set SELinux as permissive. Since I'm not an android dev, only an ambicious amateur, I can't really explain what it does or what happens when you do that. So far, neither me or my phone died because of that, so.
Oh by the way, whenever you insert the pen , Android will say it's corrupted and ask you to format it. DO NOT DO IT! That happens because Android doesn't natively support NTFS (hence using an external app to solve that). Oh, and since we're talking about that, there is a way for Android to natively support NTFS...
..., just search it up on XDA. Beware that it's outdated and it won't work on Marshmallow either, unless you edit the copymodulecrc script, but that goes beyond my knowledge. For now, stick to the plan.
4th step - You need to choose the folder which you want to mount the pen to, which will be a folder in the root Android folder (I chose /pen so that I wouldn't forget)
You are now probably thinking, "That's insane! You need to edit init.rc in order to do that!" Well, you're kinda right, but there is a workaround for that. Why do I do this? Well...
... if you mount the pen in another random folder such as /storage/emulated/0/pen it won't work because all the folders underlying that one have certain permission issues that don't let other media apps be able to search for music files.
So here I'll show you two ways of accomplishing this.
4.1 Editing init.rc - This is very complex and NOT RECOMMENDED unless you're very comfortable with messing with boot files. PLEASE DO NOT DO THIS if you aren't sure of what you're doing, don't tell me I didn't warn you.
So in order to do this, well, I won't explain it to you. Search it up on the internet, it's very complex and too big for me to post here. But in the end what you want to do is edit the init.rc file, adding two lines:
"mkdir /pen" and "chmod 777 /pen".
4.2 Creating a script that runs on boot - This is the one method I recommend since it's harmless, but you have to install yet another app, that allows you to run scripts at boot. I used script manager. Then create a script that mounts the / folder as rw, creates the folder /pen, chmods it to 777. I used the following:
#!/system/bin/sh
su -c mount -o rw,remount /proc /
su -c mkdir /pen
su -c chmod 777 /pen
I tried other mount -o commands with rootfs instead of /proc but they didn't work. I don't know the difference but I hope it's harmless. Anyways, let's move on.
Run the script to see if it works, and to create the folder. Use a rooted file explorer to verify if the folder was created.
5th step - Reboot your phone if you had to set SELinux as permissive, and type on the Terminal "su -c getenforce" to confirm that your SELinux is permissive.
VERY IMPORTANT - On the Paragon app, open settings and disable FS access rights, otherwise it's the same as mounting a Fat32 pendrive - not what we want.
On the Paragon app, choose the folder we created before as the folder to mount the pen to, and mount the pendrive. If you followed all the previous steps correctly, the app won't have any issues mounting the pen.
6th step - Find a way to enforce Android building a media library with the new files in the USB OTG pendrive. There are many ways to do this and I recomment the one I used, but I will tell you other ways.
I used the app jetAudio which is a media player that can also forceably build a media library. On jetAudio settings menu, press "Rebuild media library" and point to the /pen folder. It will start reading all the files and Android now detects your pendrive as a media library.
Another way would be to use an app called FolderMount, and creat a symlink from the /pen to another folder in your emulated SD storage (you know, the only folder you have access to if you're not rooted), and wait for some time until hopefully Android detects your new music. If you don't want to use FolderMount, do a symlink with another method (like the ln command)
EDIT - Another cool way I found elsewhere on StackExchange is to run this command (through a script or whatever):
am broadcast -a android.intent.action.MEDIA_MOUNTED -n com.android.providers.media/.MediaScannerReceiver (-d file:///pen)
which forces Android to run a media scan. The part on parenthesis is optional, you can use it to choose the folder in which Android runs the media scan.
Hurray! Congrats for reaching this part of the post. If you did everything correctly, all media apps will finally be able to find the files. I posted some screenies to orientate you.
Feel free to ask anything and I will try to answer or explain. Remember that I'm no Android dev so my knowledge is limited. Feel free to thank me, if you want too.
reserved post
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...
Ok, you may be right with apps which are not yet updated to support Marshmallow, I didn't check that.
gaferreira13 said:
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...
Click to expand...
Click to collapse
Oh, and maybe now that I think of it, this could solve the problem, since mounting/unmounting is done with the Paragon app instead of Android. Give it a shot
AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
Using native otg function, you can only copy files between phone and otg dive. To open a file e.g. To install apk from otg, you have to first copy it to phone's storage. On many media player, video can only be played sequentially (seek bar doesn't work).
Stuck at step 4.2, folder is not created
kashinath said:
View attachment 3746340Stuck at step 4.2, folder is not created
Click to expand...
Click to collapse
Hey, is there any way for you to determine the path of your root folder? Maybe using ES File Explorer. For some phones, the root folder isn't pointed to /.
EDIT - If you can't do that, try replacing the first of those commands with the following:
su -c mount -o rw,remount,rw /system
I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.
Viridis said:
I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.
Click to expand...
Click to collapse
Yeah forget mounting anything in the /storage/emulated/0...
According to the post you linked in your comment, "6.0 mounts to /mnt/media_rw/ but I can't seem to get any media players to see it. I tried creating a symbolic link in /storage/emulated, but I get an error with root explorer about symbolic links not being supported" which is exactly what happened to me
If you don't like the folder mount alternative you can always do a bind command (but i'm not sure how it works), search it up and see if you get any results.
Is your pen in Fat32 though?
There is a workaround for the pen thing... If you use Total Commander and want to edit any files in /, it asks you to run a command that mounts the / folder. Try to see what command it is and replicate it into the script, then the rest might work.
Thank you so much !! It worked on my XT1033 falcon dual sim - MM6.0 identity crisis 1.3a . I can finally restore all my nandroid backups.
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777
4k5blr said:
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777
Click to expand...
Click to collapse
No, thank you
And, damn you're right, lol I'll correct it ASAP, thanks a lot for pointing it out
I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)
Arcane35 said:
I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)
Click to expand...
Click to collapse
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps
gaferreira13 said:
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps
Click to expand...
Click to collapse
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.
Arcane35 said:
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
Click to expand...
Click to collapse
Ooooh. Remember the topic is called "Full USB OTG on Media Players in Marshmallow"
I can't help you then, sorry. The only thing I can tell you is to open the /proc/mounts file as text on the top there should be a command that tells android to mount the root folder as rootfs I believe.
Maybe that could help.
Arcane35 said:
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.
Click to expand...
Click to collapse
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.
gaferreira13 said:
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.
Click to expand...
Click to collapse
It is set as 0777, so yes (if the 0 is not supposed to be there)
Arcane35 said:
It is set as 0777, so yes (if the 0 is not supposed to be there)
Click to expand...
Click to collapse
Hmm... If you can open the folder fine and maybe create a file in there or something then I can't help you any further. The paragon app doesn't let you do much regarding troubleshooting.
Try using the methods that other people did like using Foldermount or something like that.