Why cannot I browse the root folder, yet could with stock android? - LineageOS Questions & Answers

I have the following setup:
[ROM][7.1.2][OFFICIAL] LineageOS for N7105 by PoisonNinja
open_gapps-arm-7.1-pico-20170803
addonsu-14.1-arm-signed
And have followed the instructions to the letter, including wiping the internal storage and external SD card. I have also enabled root access in the developers menu. I have installed two different pieces of FTP server software. One called com.theolivetree.ftpserver and the other lutey.FTPServer, unfortunately I am not able to access the SD card at all through either pieces of software, furthermore which I think may be the root cause (haha) of the problem, I am not even able to browse the root folder after sucessfully connecting. This was not the case when I was running stock 4.4 android without root - granted I could not do anything with it, but could browse the root folder and all sub-folders. Flashing LineageOS seems to have made it now impossible to even view the root folder - is this some option?

Related

SD cards are not reachable

Hello!
First I don't really have much experience about android. (I know it is not a good start)
About a month ago I bought a note 8.0. I also bought a 64 GB SD card. I would have liked to use the SD card with root access for all applications.
So I rooted the device and I installed and ran SD KitKat fixer. It was not success. I found this article: winaero.com/blog/unlock-external-sd-card-writing-for-all-apps-in-android-4-4-kitkat I did the steps but I couldn't modify /system/etc/permissions/platform.xml not even with file explorer (with root permission). I could save the file but the file didn't changed. After that I made a mistake. I copied the file to the other partition. I changed the file and copied back to the original location. (I left an oroginal copy on the SD card but it could not be reachable after the change) After this the device could not read or write any of the sd card partition except the system partition. I connected the tablet to my PC, I see the SD cards, I can open them, but they are empty and I can't write them. In the system setting (on the tablet) the SD cards are visible.
1. I tried to modify back the XML file but I can't open it with file explorer.
2. I reset the the tablet. It didn't work.
3. I tried to connect the device to Samsung kies. I wanted to make fore reinstall but kies couldn't build the connection.
Error message:
Failed to connect device.
Connection or use may be restricted if the device access (including writing)
is prohibited by your computer's security program, or for any other reason.
4. Keyboard is not working I connected one with USB. I can connect to my wifi network. I tried to connect to google play. It accpeted my login datas but it couldn't connect to google servers.
Because I can't write the drives of the tablet from my PC, I can't copy a rom to the device.
File explorer is not working on the device. It can be opened but nothing can be seen.
I think I can't take back the tablet where I bought it beacuse I lost the warranty with the rooting.
Can anybody give me advice what should I do?
Could somebody please make available the original platform.xml for me?

Accessing ext. SD-card via Wifi

Hi all,
I like to acces my phone via WIFI to upload & download files to it . I use the Websharing App to do this and this works quiet well via a browser on my computer.
However when trying to write a new folder to my external SD-card in my phone, i get an error. I Tried this with different filesharing apps, but i seems like i don't have persmission to do this because i always get the same error.
This problems occurs only when trying to write something to the external SD. Reading & copying is possible.
Does somebody knows how i can fix this problem ?
When connecting the computer via usb-cable , it's possible to write directly to SD card.
(Samsung galaxy s4 mini LTE, android 4.4.2)
Cheers.
On android 4.4.2 3rd party apps can't write on SDCard. You must root Your phone, install Xposed Framework and then download and install module KitKat SD Card Full Access. Also better way to browse and manage files directly on Your phone is SambaDroid, You can even manage system files.
Chamelleon said:
On android 4.4.2 3rd party apps can't write on SDCard. You must root Your phone, install Xposed Framework and then download and install module KitKat SD Card Full Access. Also better way to browse and manage files directly on Your phone is SambaDroid, You can even manage system files.
Click to expand...
Click to collapse
Okay thanks for your help. Will try sambadroid, otherwise will check the xposed framework. Phone is already rooted.
I'm afraid that You also need this xposed module for Sambadroid to work. As I remember it was some build.prop modification to make it work if You don't wanna play with xposed.

Unable to browse internal storage.

I can't browse my internal storage on my phone. I've tried it with 4 file browsers 2 of them require root and the other 2 don't. When I go to /storage/emulated it's empty even tho 2 days ago there was files there. I can still access my photos and videos even tho they are saved there but I can't get there with any file browsers.
I am running stock rooted marshmallow.
Sheeppo said:
I can't browse my internal storage on my phone. I've tried it with 4 file browsers 2 of them require root and the other 2 don't.
Click to expand...
Click to collapse
File browsers only require root, in order to access specific restricted partitions (such as System). Most will work fine without root, just the functions that require root won't work.
Try going into phone Settings, Apps>Permissions, and make sure the file browser has permission to access storage.
All good now
I decided to install viper one and everything works now

Is there any way to get write permissions to SD card - xposed Fix EXTSD dont work

I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
louiscar said:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
Click to expand...
Click to collapse
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
ashyx said:
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
Click to expand...
Click to collapse
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
louiscar said:
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
Click to expand...
Click to collapse
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
ashyx said:
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
Click to expand...
Click to collapse
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
louiscar said:
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
Click to expand...
Click to collapse
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
ashyx said:
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
Click to expand...
Click to collapse
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
ashyx said:
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
Click to expand...
Click to collapse
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
ashyx said:
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
Click to expand...
Click to collapse
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
louiscar said:
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
Click to expand...
Click to collapse
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
ashyx said:
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
Click to expand...
Click to collapse
This was the method I used as soon as I updated to MM and didn't notice the "this folder is not writable" message.
However, the option to choose mnt/media_rw isn't available. If I use Detect > whole device I'll be offered :
/storage/F91E-D472/Titaniumbackup
perhaps I'd see the other option under normal circumstances but Tba is not able to access that path so wouldn't find it in a search ... I guess
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
https://www.youtube.com/watch?v=GATqU1_xzqA
louiscar said:
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
Click to expand...
Click to collapse
ExFAT. Anything above 4gb should be ExFAT.
ashyx said:
ExFAT. Anything above 4gb should be ExFAT.
Click to expand...
Click to collapse
curiously I set permissions to 777 for the mnt/media_rw and titanium can go there but any further (even though I've done the same for the sdcard folder - nada!
and sadly after converting to exfat - mnt/media_rw .... "this folder cannot be accessed"
Not sure what else I can do.

How to root Samsung A3 (2017) - Guide

I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
Make sure to have installed on your PC Samsung USB driver for mobile phones, available on Samsung website.
I used different versions of the files needed (that guide is for Samsung 8). With the following files, everything worked well:
twrp-3.4.0-0-a3y17lte.img.tar
no-verity-opt-encrypt-6.0.zip
RMM_Bypass_v3_corsicanu.zip (learned this from another guide on this forum)
Magisk-v20.4.zip
Once TWRP is installed, the guide instructs you to install no-verity, then reboot to recovery and immediately after that reboot to system; only later, transfer and install magisk. THIS MESSED UP everything, in my case at least.
The solution was even faster: once TWRP is installed
plug USB and transfer all needed files (listed above) at once
install no-verity and reboot to recovery;
install RMM_bypass and reboot to recovery;
install magisk and reboot to recovery
reboot to system
Now you proceed following the rest of the guide.
After rooting, you may want to fix a few problems you may encounter: see next post.
HOW TO FIX FINGERPRINT AFTER ROOT
When your Galaxy A3 is rooted, unfortunately fingerprint will not work properly to log in on your apps (but it will work to unlock your phone). To fix this:
install from Google Play a file manager (like Solid Explorer)
in the left menu select ROOT folder, then rename
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apk
to
/system/priv-app/SamsungPass_1.3/SamsungPass_1.3.apj
remove /data/app/com.samsung.android.samsungpass-1
reboot
This will remove SamsungPass. You will not be able to use SamsungPass anymore on your rooted phone, so forget the ability of saving passwords on websites and confirm them with fingerprint (you can still save passwords in browser or use google autofill; you just can't confirm them with fingerprint).
But, with the method above, at least you will be able to use fingerprint to log in those apps which natively support fingerprint login (like banking apps).
HOW TO MAKE BANKING APPS WORK ON A ROOTED PHONE
...Banking apps, though, tend to stop working when they detect a rooted phone. You can try to fix this using Magisk Hide feature.
Open Magisk and tap on the shield icon
Tap MagiskHide
Check your bank apps and any other app that want to prevent from detecting root. (According to the guides I read, hiding too many apps can be a problem: stick to what is really needed).
HOW TO MOVE WHATSAPP MEDIA FOLDER TO SD CARD
This was the main reason why I decided to root my phone: I was running out of storage. So I bought a high-quality and fast sd card (yes, it deserves your 20 €) and did the following:
Download "Apps2SD" (the original by Vicky Bonick; it's free) and follow instructions on how to create partitions.
You can create upto 3 partitions: 1st fat32/exfat/f2fs/ext4/ext3/ext2 (it's your SD card), 2nd ext2/ext3/ext4/f2fs (it is used to link the apps), 3rd swap partition (it's optional).
IMPORTANT: With Apps2SD you can LINK apps (they will end up in 2nd partition) or use FOLDER MOUNT (the chosen folder will end up in 1st partition, the one that looks like your normal SD card).
Please note that for Whatsapp media folder you will use FOLDER MOUNT method: so it will end up in the 1st partition. Create the 1st partition large enough for your whatsapp media.
Use "folder mount (app analyzer)" feature: it's like folder mount, but it's pre-set for some common apps, including Whatsapp. With this feature, you can successfully move Whatsapp media folder to SD, in one clic.
To understand what folder mount means: see FAQ.
In my case everything worked fine. When I reboot I have to re-mount folder, but it takes one second (just open Apps2SD, tap Folder Mount, slide "whatsapp other").
By the way, with App2SD you can do much more: you can move virtually any app to your SD card using the "Link apps to SD card" feature, as explained in Vicky's video.
...Hope this will save you some time!
airali said:
I successfully rooted my Samsung Galaxy A320FL following more or less this guide (I know, it's a video and that's annoying, but it's also very clear. And there is a text version linked in description), with some modifications though.
I will write here what differs / is not specified in that guide.
I also attach all the files I used; they can also be found on the internet with some search.
(...)
Click to expand...
Click to collapse
Thank you! I successfully used your compilation for a T-Mobile branded unit, all works after some tinkering. I didn't have the fingerprint problem, possibly the Samsung security thing is not the same on the carrier-modified ROM.
I had problems first making root work because of the succession of operations - basically, everything needs to be formatted in TWRP so it can mount partitions. Once I boot up the ROM, TWRP won't mount anymore → every zip you want to install, you need to do in one go before you reboot to Android.
I tried to root mine, but it didn't show up in odin, it did show up in device manager but I can't do anything with it, no transfering files via usb, etc.
The drivers are installed, I reinstalled them a couple of times, tried a different USB port, etc...
No sucess so far, I hope someone here can help me
Tap tap tap

Categories

Resources