Database Users

[Problem] No "sdcard", only "root" folder :(

Hello,
it's a little bit difficult to explain my problem. it started few days ago when my 7.7 didn't turn on.
Then i read about the trick to press the power button longer than 10 seconds and it really worked. First I was glad but then i found out, that my picture gallery and my mp3 player was empty!
First I thought that everything was deleted, but that wasn't true. The files are still there. In fact it seems that the system has changed the "/sdcard" area to "/root". So the apps can't find the files.
I uploaded a file where you can see what i mean. On my Smartphone is also a "/sdcard" instead of the "root".
My 7.7 is rooted, no other modifications have been made...
Who can help me to solve this problem without doing a reset to factory setting..

That's just how the stock file browser shows it, it's not actually mounted at /root.
If the gallery and music player are empty you could try giving it a little time for the media scanner to add your media. If it doesn't show up, then wipe the data of the media storage app and restart your tab. You may have to restart it again after it has built its database to get everything working properly.

i wiped the data, didn't work
what if the internal storage is really mounted as /root now? what can i do to change it?
because the empty gallery and mp3player aren't the only problems now. if i take a picture, i cannot use the preview to look at it. it says "no elements" then. so i think its a problem more deep in the system...
i really dont understand how this could happen, i just turned the tab on..

If you have ES File Explorer, it should show that same "root" folder as actually being the internal "sdcard" folder. I don't think it has anything to do with actually being rooted, it is just how the built in File Manager lists the folder.
Another option, perhaps Fix Permissions in Recovery may fix your issues.

can i find a tutorial to fix permission in recovery mode?

Need help with understanding mount-points, folder structure and file system rights...

Hi everyone,
I need your help. I sometimes face strange issues with my Nexus 4 (Stock Room, Rooted, Matrix Kernel v5). Yesterday I wanted to copy a apk-file for installation on my phone from my home-server. I use ES File Explorer for that. I failed to copy the apk-file to /sdcard/folder-name (operation failed). then i navigated to /data/media/0/folder-name and tried it from there, also it didn't work.
i then copied the file to /sdcard/download and was able to copy it to that and to install it.
i don't really understand why it behaves that way, i was always able to go to /sdcard/folder-name and do what i want. i also noticed another strange thing. i connected my phone via USB (MTP-mode) to the PC and uploaded a few GB of MP3s to it (Folder: Music).
when browsing this folder with ES File Explorer, I cannot delete anything from that folder /sdcard/Music. THOUGH it reports "deletion successful" the files or folders do not get deleted but just remain on the internal SD-card. i could only delete the music successfully via "/data/media/0/Music".
who can explain briefly WTF is going on? i obviously do not really understand the concept and logic behind this. is there a maximum file/path length that must not be exceeded?
thanks in advance and best regards,
hallu

need to bump this, sorry...

does anyone have any idea as to why this phone is behaving the way it is?

I use root explorer and have ZERO issues. That includes pulling apk's.

Try a different file explorer to see if that makes a difference so at least you can determine if the issue is just app specific and not something else.
Check to see of ES isn't mounting certain folders with RW permissions.
Also the actual internal storage is /data/media/0/ so /sdcard/ is just a symlink to that folder. ES seems to be having problems with the symlinks.

extsdcard write issues

Issues with wanting to copy to extsdcard any new files/folders from my gdrive account...not specific to write or modify but a mix of both.
I am experiencing an issue with my 32gb sdhc card that baffles me. I use ES Explorer and create a folder on the extsdcard and it quickly shows creating the folder in asynch mode, I then refresh and it shows up. Ok odd, whatever, moving on... I then try to delete it and it says successfully deleted, hit refresh and it shows up. How is this?
Another test is use FolderSync and i set up the folder pair and then click sync. Status shows error in red, I click show to see errors and I see errors "could not create folder: <anyfolder> File transfer failed '<file>' open failed: EACCES (Permission denied)"
Anyone have issues like this? Any pointers? I have researched and cant find much other than 4.4 changed its extsdcard security.
Thanks
Robert

Kitkat is picky on third party apps writing files to the card. Call it Googles strive to be more like Apple with each release.
Google probably wants all users to be cloud loving lemmings they can data mine.

http://www.androidpolice.com/2014/0...at-and-even-samsung-may-be-implementing-them/

My main issue is I can't even delete a folder. ..
Sent from my SM-G900V using XDA Premium 4 mobile app

Dunno if it's just me.....I've had zero problems doing ....well....anything I want to ?!?
BTW, I used ES file explorer (file exploder?) on my Galaxy Nexus.....constant issues and crashes.
Never again.
On your S5 there is a app called "My Files", it seems to work almost exactly like ES is supposed to work.
It does everything I can think of....make folders, open and add to them, delete files and folders ???
Works perfectly on mine with a 32gb Pony class 10 micro SD, not a single problem ever.
Perhaps you have a problem SD card ?
<edit>
Err, it's a PNY sd card, just always seemed like calling it a Pony was the correct term ?

As soon as Verizon gets root run the app
SDFix
From the market, or you need to edit platform.xml and add in a permission, only takes a few seconds but you need to be rooted, it is an issue with kit kat

I/O bug? File deleted, but storage space doesn't change.

12/21：today I copied a video file about 1G from my PC to 5T, using MX player to watch it, then I used OOS built-in file manager to delete it……OK, yep, Hi……I/O bug again.
-------------------
OOS 4.7.5
Yesterday got my 5T, rooted and installed root explorer. When I deleted some big file like OOS 4.7.5 zip via it, I found the space left no change, only way is a reboot.
The issue happened once on my OP 3T, not only using Root explorer, all 3rd party file explorers like ES, Solid Explorer , have the issue. But oneplus fixed it in update later.
ref:https://www.xda-developers.com/io-bug-on-oxygenos-4-is-causing-deleted-files-to-still-take-up-space/
Anyone same here on 5T?

Iwbtone said:
OOS 4.7.5
Yesterday got my 5T, rooted and installed root explorer. When I deleted some big file like OOS 4.7.5 zip via it, I found the space left no change, only way is a reboot.
The issue happened once on my OP 3T, not only using Root explorer, all 3rd party file explorer have the issue. But oneplus fixed it in update later.
ref:https://www.xda-developers.com/io-bug-on-oxygenos-4-is-causing-deleted-files-to-still-take-up-space/
Anyone same here on 5T?
Click to expand...
Click to collapse
I may have experienced this yesterday. I'm on 4.7.4 stock. I had been copying files, firstly from my PC to the phone, then from a micro SD card to the phone. In each case I was moving game data to Android/OBB so I didn't have to download it all over again, meaning I would only have to download the app from the Play store. This didn't work as normal, and then when I tried to delete the data using ES file explorer, the app couldn't 'see' it in the first place. The built in file explorer could but I don't think the storage space changed until after I rebooted. After copying the game data over again, rebooting and then downloading the app from the Play store, only then did game see the data in OBB. Something odd was going on but I was only half paying attention, especially to the remaining storage space.

Ouzo said:
I may have experienced this yesterday. I'm on 4.7.4 stock. I had been copying files, firstly from my PC to the phone, then from a micro SD card to the phone. In each case I was moving game data to Android/OBB so I didn't have to download it all over again, meaning I would only have to download the app from the Play store. This didn't work as normal, and then when I tried to delete the data using ES file explorer, the app couldn't 'see' it in the first place. The built in file explorer could but I don't think the storage space changed until after I rebooted. After copying the game data over again, rebooting and then downloading the app from the Play store, only then did game see the data in OBB. Something odd was going on but I was only half paying attention, especially to the remaining storage space.
Click to expand...
Click to collapse
yep, actually I also don't pay attention at the first place.
But I tested later, copy some big file like a video clip sometims via Root Explorer, then I can see the storage space left is smaller. Test to delete file copy A clip via RE, storage space no change. Test to delete file copy B clip via OOS file manager, storage space reclaimed. Only after a reboot , original copy A clip space reclaimed.
So every one can test it easily and quickly to see if the issue is there on 5T. If true, then I'm disappointed about this thing, because it was fixed before, how can an old bug rebirth:silly:

I can second this. There was a SDCARDFS disabler or something released by @eng.stk as a Magisk module. I am tempted to dig it out to give it a try.
EDIT: If anyone wants to try this:
https://forum.xda-developers.com/showpost.php?p=71671217&postcount=4123

pretty sure there was a very similar bug on 1+5 that got fixed at some point. And if I recall correctly the fix was something to be added to the build.prop.
Need to dig tin the 1+5 forum.
---------- Post added at 14:00 ---------- Previous post was at 13:50 ----------
dreinulldrei said:
I can second this. There was a SDCARDFS disabler or something released by @eng.stk as a Magisk module. I am tempted to dig it out to give it a try.
EDIT: If anyone wants to try this:
https://forum.xda-developers.com/showpost.php?p=71671217&postcount=4123
Click to expand...
Click to collapse
As far as I can tell that module would remove ro.sys.sdcardfs property, which doesn't look to be present in the actual build.prop.
Maybe setting "ro.sys.sdcardfs=false" could do the trick?
---------- Post added at 14:57 ---------- Previous post was at 14:00 ----------
So, the issue I was referring to was:
https://www.xda-developers.com/io-bug-on-oxygenos-4-is-causing-deleted-files-to-still-take-up-space/
And the actual fix was to remove that "ro.sys.sdcardfs" property. Which is not there on 5T already.
I'm gonna try to change that to "false" instead, and see what happens.
EDIT: I was working under the assumption that was happening for me as well, but looks like everything is working fine on 4.7.5 with space being cleared as soon as I delete a file.
But, at least, adding "ro.sys.sdcardfs=false" to build.prop didn't break anything.
Which version are you on?

And I just found when I use Root Explorer copy one file , then using OOS file manager to delete it, the issue is still happening.

The fix with the Magisk module did not work, changing the prop to false instead of deleting also did not work.

Reading this I thought I might had tested for the I/O bug when I got my hands on the device. Couldn't remember for sure so went back for testing purposes.
I/O bug is present on 4.7.4, tested.
I/O bug is present on 4.7.5 as far as i see reported here, I never updated to it.
I/O bug is not present on 4.7.2. tested.
So it seems as it was introduced somewhere between 4.7.2 and 4.7.4.
Well done OnePlus...

I am on 4.7.5 and I can't replicate this problem. When I delete any file, the overall storage size is reduced accordingly and instantly. Tried with both Mixplorer and Solid Explorer.

What format do you have for data? ext4? f2fs?

dreinulldrei said:
What format do you have for data? ext4? f2fs?
Click to expand...
Click to collapse
Shouldn't make any difference...
BigBrosMo said:
I am on 4.7.5 and I can't replicate this problem. When I delete any file, the overall storage size is reduced accordingly and instantly. Tried with both Mixplorer and Solid Explorer.
Click to expand...
Click to collapse
I'm double posting because... You quoted me on another thread. Sorry XDA.
I have not personally tested on 4.7.5, but it was on that build that @Iwbtone first found the storage bug so I have to take his word on that.
I tested it on 4.7.4 and bug is present.
I reverted to 4.7.2 no bug to be found.
I tested with both Root Explorer and Solid Explorer, but any external file explorer will trigger the bug.
Also random installed apps deleting files might trigger it.
Workflow for testing purposes.
Copy any OOS Full ROM zip file to any other location, check used storage on Android settings.
Delete the new copied file with an external file explorer app and get back to Android storage settings.
The used storage remains as if you haven't deleted the zip file.
Some media files might get past the bug, I have not tested that on the OP5T and don't really care at this point, but that sometimes happened on the OP3/3T giving us false positives for cleared storage while the bug was still present.
There are 2 reports of bug not, yours and @maddler.
Would be nice to double check this with the workflow I shared here.

Yup. Deleting media files, ok. But deleting zip files, bug exists.

can someone try running trim command when you delete the zip and see if the problem persists after the command

virtyx said:
can someone try running trim command when you delete the zip and see if the problem persists after the command
Click to expand...
Click to collapse
No. Hardly related. Shouldn't make any difference.
By the way. I/O bug is still present on 4.7.6.
We are doomed. ?

[NST/G] Revisiting cacerts.bks

cacerts.bks updated 12-6-20
When the original search was on to repair the aging cacerts.bks file in order to get the Kindle app working again, one of the things I came across was a remark from a fellow who had located a Honeycomb ROM (Android 3.2...last stop before the format of the security certificate storage was changed) and copied the cacerts.bks file from it to his Android 2.2 device which was having problems with websites, etc.
I still can't get the method described by @tshoulihane in this thread to work for me. But his edited cacerts.bks file works really well in solving the problem.
Yesterday I managed to locate a CM 7 ROM (Honeycomb). It contains a largish cacerts.bks file (compared to ours) with 127 certificates, 17 of which have expired. These seem to be mostly for central/eastern European and Asian entities, so perhaps not that critical. Well, it's only 10 years old
It has worked for me with the Kindle app and perhaps will help with some of the websites that complain about a secure connection even though I have enabled TLS 1.2 in Opera Mobile. More testing is needed there.
For anyone who wants to try it out, it is attached below. To use, rename your current cacerts.bks file (that's in /system/etc/security) to cacerts.bks.bak or similar. Then move the new file (unzip) into the same place. Check permissions. They should be rw-r-r. Reboot.

This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?

xrayd2 said:
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
Click to expand...
Click to collapse
So was your SU app missing? Or did your file manager just not have root access?
Hard to know where to start. From my experience, the best-behaving SU for the NST/G is the one that comes with NookManager (attached below). It's old and the binaries are probably out of date, but you don't need anything better for the device.
You can try removing the one you have now, reboot, and install the one below. Then check that your file manager has root acccess. In ES File Explorer, for example, you have to go into settings and tick the selection for root access. It's not automatic. And even with that, you have to tick an additional box to mount /system as rw while you're working in it.

At one time the superuser app was included -- but is no longer linked, and I had overlooked it after initially flashing the rom.
Unfortunately, the su app you provided also doesn't work. When I try to delete the old cacerts.blk it looks like it's doing something, but then the file still remains. If I instead try to rename the file, I get "operation failed".
I tried to delete or rename using an app called "root browser", and also the file manager in "super manager" suite. When I try to enable the root explorer function in ES file manager , I get "sorry, test failed. This feature cannot run on your device."
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
I appreciate your help though!

xrayd2 said:
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
Click to expand...
Click to collapse
Mmm.... so the ROM came "rooted"? I've attached a root check app which I've tried on my NST. This should answer the question of root.
If root has been lost somehow, it might be possible to salvage what you have by running NookManager. If you don't want the various additions like Relaunch, you can remove those apps from the data/app folder once you've written the card and then make the other needed changes as described here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Or, you could just use NM as-is and uninstall unwanted material afterwards. The important thing is root and a functioning SU.

Okay... turns out my device was NOT rooted after all; I had assumed the binaries were already installed. Fortunately, I was able to find a superSU 0.93 binary and root through CWM. I replaced cacerts.blk with yours, and now the kindle app works! At first I had difficulty logging in, but turns out Amazon was emailing me a one time password after every attempt. After entering the OTP I am now up and running.
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Thanks for the link to your other post. I will sideload the apk's you recommended.

xrayd2 said:
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Click to expand...
Click to collapse
Might not be possible. Chatter here: https://forum.xda-developers.com/showthread.php?t=1604661&page=2 goes back to 2013.

I found reference to a functioning version in 9/2016. Had hoped it was a cacerts issue but maybe pocket changed their api.
https://forum.xda-developers.com/showpost.php?p=68600731&postcount=54

Would this be what's causing my Nook to not load certain https sites?
I can get to gmail fine, but I can't for the life of me load the todoist website
Tried loading your cacerts.bks, doesn't seem like it changed anything

I had no problem getting the Todoist home page. Logging in may be another matter.
Are you using Opera Mobile and did you make the settings change for TLS 1.2?