Where does LineageOS save its updater files. CM used to save them in /sdcard/cmupdater, but I can't find the LineageOS versions. I want to exclude this folder when syncing my device to external storage. Thank you in advance for anyone who can help answer this question.
/data/data/org.lineageos.updater/app_updates
Thank you! I did a search with ES File Explorer for the nightly update file but it did not find it.
If you are looking at ES File Explorer, are you in recovery mode? I believe the file(s) in question are in a folder in the recovery space, not the regular system / data space. If, for example, you are using TWRP, use the built-in file manager. Hope that helps.
Please note, this value has since changed (Late August, I believe, or early September).
Specifically, while it used to be /data/data/org.lineageos.updater/app_updates
it is now /data/lineageos_updates
Related
Hi all,
Thanks for helping me out with this. When Jelly Bean was first announced I tried an unofficial ROM that was very buggy, so I went back to an AOKP ICS build. Since then I switched to CM 10.0 and continued to use it for a while until I heard about the recent Paranoid Android builds so I decided to give Jelly Bean another shot.
As we all know, Jelly Bean places its files inside a folder titled 0 (Zero) on the phone. When I upgraded the first time, all my files were automatically moved into the 0 folder and when I downgraded, they did not move back but I could still see and access the 0 folder with my old files in it. So far, so good.
Since I was using that configuration for a month I took a lot of photos and downloaded some files that I definitely don't want to lose. So imagine my surprise when I installed Paranoid Android and I could no longer access my old pictures and files!!
My guess is that the files are still on the phone's memory, but since the operating system now sees 0 as its root folder, it isn't aware of all the files existing outside that directory and can't physically access them using Astro or Android File Transfer (or Windows Explorer).
So my question to the amazing community here is this:
How can I access 100% of the phone's internal memory?
I assume there is a way to do this from recovery, but I don't want to do something that could potentially delete those files before I get to copy them to my computer and the folders inside the 0 directory.
Any and all help is appreciated! Thank you!
Use a root explorer (like ES File Explorer) and move the files into the relevant folder under 0
Hi,
i have the same problem than you ><,
appeared after flashing nightly CM10.1, the only solution to remove the folder "0" than I found is to save everything (by ftp because by usb connection I did'nt see my file) and formatted the sdcard ... not clean solution...
EddyOS said:
Use a root explorer (like ES File Explorer) and move the files into the relevant folder under 0
Click to expand...
Click to collapse
ES File Explorer is not working for that. It still doesn't see the old folders. Any other suggestions?
I tried using ClockworkMod recovery and selecting "Mount Storage" while connected to my computer but when I click "Mount Storage" nothing happens. Any help with this would be appreciated, because when I browse using ClockworkMod Recovery (like for a .zip to install) I can definitely see the old folders with the old files in them.
Let me start by saying that i do not take credit, by any means for this fix, i did use the SEARCH tool and found the solution. What i'm doing is posting a faster/easier fix for the thread here http://forum.xda-developers.com/showthread.php?t=2196200
All of the help i read, is from this thread here http://forum.xda-developers.com/showthread.php?t=2102981&highlight=miui+camera.
Our common issue was that each time we flashed an AOSP ROM(for me the new MIUI PORT FROM SPRING TO SHG3 TMO) the camera wouldn't connect, and that's a deal breaker. Im sure it was for many of you. (I'm a noob, just giving a heads up, and this is why i have to post here rather than the first thread, being understandbly limited and all) As the 2nd of the two threads says, the issue is that on stock rom there is a bin file named SlimISP_ZH.bin, once flashed, it's no longer there, causing the camera to simply not connect. I odin'ed back to stock(because i didn't have access to the bin file), used ES File Explorer to "copy" the SlimISP_ZH.bin file into my external sd card, then i proceeded to flash to the MIUI ROM of my choice, after setting up the phone, using ES File Explorer again, i placed the bin file on the /data directory. If a mod can confirm it's ok, i'll be more than happy to upload the bin file to make it easier. Oh one last thing i changed permissions, so it should show as rw-r--r--
fmanila said:
Let me start by saying that i do not take credit, by any means for this fix, i did use the SEARCH tool and found the solution. What i'm doing is posting a faster/easier fix for the thread here http://forum.xda-developers.com/showthread.php?t=2196200
All of the help i read, is from this thread here http://forum.xda-developers.com/showthread.php?t=2102981&highlight=miui+camera.
Our common issue was that each time we flashed an AOSP ROM(for me the new MIUI PORT FROM SPRING TO SHG3 TMO) the camera wouldn't connect, and that's a deal breaker. Im sure it was for many of you. (I'm a noob, just giving a heads up, and this is why i have to post here rather than the first thread, being understandbly limited and all) As the 2nd of the two threads says, the issue is that on stock rom there is a bin file named SlimISP_ZH.bin, once flashed, it's no longer there, causing the camera to simply not connect. I odin'ed back to stock(because i didn't have access to the bin file), used ES File Explorer to "copy" the SlimISP_ZH.bin file into my external sd card, then i proceeded to flash to the MIUI ROM of my choice, after setting up the phone, using ES File Explorer again, i placed the bin file on the /data directory. If a mod can confirm it's ok, i'll be more than happy to upload the bin file to make it easier. Oh one last thing i changed permissions, so it should show as rw-r--r--
Click to expand...
Click to collapse
How do you change permissions? Do I need to be rooted? Do I need busybox?
dbwlaw said:
How do you change permissions? Do I need to be rooted? Do I need busybox?
Click to expand...
Click to collapse
Yes you need to be rooted. No you do not need busybox. Use ES File Explorer. Better yet, try Fix Permissions in Custom Recovery.
file
can you please provide me the file
email: [email protected]
So I can't seem to figure out how to do this I download the proper files and everything I go into TWRP and go to flash the zip file only problem is the zip file is nowhere to be found I have a Samsung Galaxy S3 Tri-Band (model #L710T) (Running Oct Os) Anyway moving on every time i go into recovery mode my storage option at the top is stuck on internal storage I can't change it every time I try to change it to micro SDcard nothing happens then the file path is just this icon ---> (/) then the folders available are boot, cache, data, dev, etc, external_sd, license, proc, recovery, res, root, sbin, sdcard, sideload, supersu, sys, system, tmp, twres, and usb-otg but when I go into any of those none of them have zip files in them as well as the file path is not the same from the one where my downloads folder is in es file explorer and the one in TWRP then i get this file path with storage/emulated/0 or something I honestly can't figure this out for the life of me and all I want is xposed so anyone who can help me I honestly do appreciate it I will be willing to post any photos or anything you need for more info and fyi my S3 is running Android Marshmallow 6.0.1 if that helps as well (mods sorry if I posted in the wrong section just signed up today as of posting this)
Try looking here.
/data/data/com.android.providers.downloads/cache
Still Did Not Work
Still did not work any other suggestions oh but I did manage to be able to select micro SD card its not stuck on just internal storage anymore but yeah that did not work.
If it downloaded its gotta be on your system somewhere. Use a good file explorer with root privileges that has a search function.
I had to search for it on mine, too. I don't remember exactly where it was, but I can narrow it down to data, sdcard, sys, or system. I am very much a noob, so I checked every subfolder in ever folder to find it. I hope that helps
Sent from my SPH-L710 using XDA-Developers mobile app
I'm running running the 4.4.2 bug fixing module if it matters.
When trying to: Download apk's, save pictures, use TB, I get an inability to access proper location error.
(Screens hots say USB storage maybe turned on.)
(TB says that storage/emulated/0/legacy can't be accessed. )
Es and other file explorers show that location as the only existing folder inside of internal storage. ("0").
Nothing else is in either folder.
I want to "restore" (Whether that be create folders, or re-flash)
EDIT: Using "Undeleter" app to recover all Archive file types (Zip, Apk, Jar.) And Image file types (there were like 8 different kinds.) Now my plan is to save it all to internal memory storage/emulated/0
I have no clue what else to do, or how to address the Legacy folder inside if "0".
Thanks in advance.
Also want to upgrade to Sm-900t/TWRP/Root/Xposed/5.0 Lollipop in the future if anyone can link a tutorial.
Would be willing to accept newest update as long as TWRP/ROOT/XPOSED are functional and Multi-Window/Pen-Window are both functional.
You could flash the latest stock ROM from sammobile.com using Odin. Then flash twrp via Odin. Flash supersu via TWRP to get root, then install xposed.
hello, since Android 13, Foldersync has no longer access to the Android/Data folder. Can someone help me or give a workaround?
Hi. If no one else has any other ideas, you can try the developer of the app. If this is the app here FolderSync, it shows the developer information as:
Developer contactWebsite
http://www.tacit.dk
Email
[email protected]
Click to expand...
Click to collapse
BiBaBuTzE said:
hello, since Android 13, Foldersync has no longer access to the Android/Data folder. Can someone help me or give a workaround?
Click to expand...
Click to collapse
Some info...
Why an Android file manager can't open folders under /Android
File managers aren't supposed to be able to access folders under /Android, but a loophole let them. Android 13 closes that loophole.
blog.esper.io
https://twitter.com/i/web/status/1560716910001520641
Lughnasadh said:
Some info...
Why an Android file manager can't open folders under /Android
File managers aren't supposed to be able to access folders under /Android, but a loophole let them. Android 13 closes that loophole.
blog.esper.io
https://twitter.com/i/web/status/1560716910001520641
Click to expand...
Click to collapse
Hi, please can you explain step by step what i must do to get access to the Folder. Foldersync needs Access to this Folder. Thx a lot and have a nice day
I haven't tried it, but this is supposed to take care of the problem, if rooted...
GitHub - Magisk-Modules-Alt-Repo/NoStorageRestrict: Remove the restriction when selecting folders through SAF
Remove the restriction when selecting folders through SAF - GitHub - Magisk-Modules-Alt-Repo/NoStorageRestrict: Remove the restriction when selecting folders through SAF
github.com
In android 13, data and obb folders are blocked. Tried many file managers with root to copy game data in obb folder but failed. Even the Xposed module "no storage restrict" did not worked. Finally copied data through browsing "/data/media/0/Android/obb". You may try this with root.
I am using Evolution X 7.1 on Redmi Note 11.
There are some file managers that are catching up with this. MiXplorer and FV File Manager have updated to allow access to /Android/data & /obb directories in Android 12+.
Now I have access to Android/Data & Android/Obb but I can't paste any file to these folders. I use ES File Explorer. I don't want to use other file manager like MiXplorer and make the trick of splitting screen with drag & drop so that to write files to the above paths. How to make it in the ES File Explorer or if it exists some magisk or xposed module in which to disable this restriction and to be like in Android 12 in which we didn't have any problem in accessing or writing any file to above paths ?
Johnn78 said:
I use ES File Explorer.
Click to expand...
Click to collapse
This is your problem right here. ES File Explorer stopped working properly upon release of Android 11 or 12. I discontinued my modded versions of the app at that time and switched to something that DOES work.
Get another file manager.
This File Manager tends to work in A13, I moved from ES a long time ago when they removed some features, https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore .
Strephon Alkhalikoi said:
This is your problem right here. ES File Explorer stopped working properly upon release of Android 11 or 12. I discontinued my modded versions of the app at that time and switched to something that DOES work.
Get another file manager.
Click to expand...
Click to collapse
When I went to Android 13 then I had ES File Explorer which didn't have access to Android/Data. Then I found ES File Explorer v4.4.0.2.1 which has the ability to have access to Android/Data but it hasn't the ability to write (via copy - paste) to Android/Data. This problem doesn't exist only to ES File Explorer but in all File Managers which I have used like File Manager+, File, MiXplorer, Xplore etc... The MiXplorer which can write to Android/Data not be done via copy - paste but via some trick by splitting screen and drug-drop the file which is some intermediate solution. If it is found some solution which can work the copy - paste to Android/Data then this will work to all File Managers which means that the problem isn't that the ES File Explorer is deprecated. May exist some magisk module or lsposed module which deactivate the SAF (Storage Access Framework) permission in which wasn't enabled in Android 12.
Johnn78 said:
This problem doesn't exist only to ES File Explorer but in all File Managers which I have used like File Manager+, File, MiXplorer, Xplore etc...
Click to expand...
Click to collapse
ES File Explorer, as I said in my previous post, no longer works with current versions of Android. This is because there is no one working on its code. No one to fix bugs when they appear. No one to ensure root functions continue to work. No one to enable proper access to Android/data.
There are file managers out there that are not ES File Explorer, and while you have tried some, you've not tried them all. I tried Root Explorer just now and had no problems copying files to /Android/data in internal storage; no tricks or workarounds needed. So I stand by my statement. Especially as the file manager I now use doesn't have this issue.