First off, though I don't know that it'd be a factor here, but I switched carriers from T-Mobile to AT&T. I don't really see how switching SIM cards would have any effect - I'd already updated to 20e, re-rooted, and installed TWRP. Double checking under Settings/Hardware Info, it shows my phone still is listed as a LG-D851.
It's been awhile since I made or checked my local TWRP backups but checking just now my TWRP folder displays as a 0 byte file. My thought was delete the file, copy a full set of TWRP folders (nandroid) back from my extSDcard and I'd be fine. Problem is I can't delete the file (and now thinking best to ask first, lol!).
I've tried with FX file manager (with root granted) but get an access denied error. Going in under System as root user and navigate to /mnt/sdcard/, I see all other folders but no TWRP file. I've tried ES File Explorer which successfully deletes it, but it reappears. Even tried deleting and creating a temporary TWRP folder immediately after but I get "Sorry, operation failed".
I'm able to get into TWRP, run a backup which says it completed successfully, but I see it as this file rather than a folder like it should be... Searching, I found one a workaround: TWRP Troubles
I use TWRP Manager free and thought about installing the latest TWRP for my D851 (from 2.8.6.0 to 2.8.7.0) but don't know if it'd create a bigger problem. Thought best to ask the pros!!
Any thoughts?
wha2do said:
I've tried with FX file manager (with root granted) but get an access denied error. Going in under System as root user and navigate to /mnt/sdcard/, I see all other folders but no TWRP file. I've tried ES File Explorer which successfully deletes it, but it reappears. Even tried deleting and creating a temporary TWRP folder immediately after but I get "Sorry, operation failed".
I'm able to get into TWRP, run a backup which says it completed successfully, but I see it as this file rather than a folder like it should be... Searching, I found one a workaround: TWRP Troubles
I use TWRP Manager free and thought about installing the latest TWRP for my D851 (from 2.8.6.0 to 2.8.7.0) but don't know if it'd create a bigger problem. Thought best to ask the pros!!
Any thoughts?
Click to expand...
Click to collapse
As I added after my initial post, if I boot into TWRP recovery and connect to my PC, TWRP shows on my PC as a folder. I'm able to copy it to my PC, but this isn't the most elegant. Is there something more I can do to get back to seeing/using folder operations on it while using an android file manager?
Again wondering if I update TWRP via TWRP Manager if that'd help any...and presumably my hardware hasn't changed any, so still would be TWRP for the d851?
Thanks!!
Related
So as of recently TWRP will not read the current files in my storage on my OG. I download new files and reboot recovery to flash, IE kernel, and TWRP still shows old files and not new ones. I've gone through and deleted old files and left only the new ones in the sdcard directory but TWRP still reads only old files. I'm using root explorer to delete/ move files, i have flashed the recovery about five times through GooManager, and have even flashed an older TWRP in fastboot. I'm stuck... any input??
What ROM are you on?
Sent from my LG-LS970 using xda app-developers app
I had this same issue after flashing CM. Had to erase internal storage.
Sent from my LG-LS970 using xda premium
janob09 said:
So as of recently TWRP will not read the current files in my storage on my OG. I download new files and reboot recovery to flash, IE kernel, and TWRP still shows old files and not new ones. I've gone through and deleted old files and left only the new ones in the sdcard directory but TWRP still reads only old files. I'm using root explorer to delete/ move files, i have flashed the recovery about five times through GooManager, and have even flashed an older TWRP in fastboot. I'm stuck... any input??
Click to expand...
Click to collapse
It will recognize the 0 folder as your SD card. You can either move all the files out of 0 copy to sdcard and delete 0, or just move stuff that you want to flash into the 0 folder. I did the latter because every time I flash aosp the 0 folder returns.
I looked for the 0 folder, but found nothing. But it did seem to happen shortly after flashed cm. Must be it I guess I'll have to format storage.
I have this problem and I can't restore or flash a rom since I can't find the files. When you say delete internal storage what does that actually do? I don't want to lose everything including my backups (which I did save on my laptop) and not be able to restore my phone. I am currently just rooted stock but did flash CM10 to play a little bit.
Put my zip files in the 0 folder and my TWRP theme in the TWRP folder inside the 0 file and it see them and works. This zero file thing is weird. I'm hoping I can get rid of it eventually.
bruiserman said:
I have this problem and I can't restore or flash a rom since I can't find the files. When you say delete internal storage what does that actually do? I don't want to lose everything including my backups (which I did save on my laptop) and not be able to restore my phone. I am currently just rooted stock but did flash CM10 to play a little bit.
Put my zip files in the 0 folder and my TWRP theme in the TWRP folder inside the 0 file and it see them and works. This zero file thing is weird. I'm hoping I can get rid of it eventually.
Click to expand...
Click to collapse
You could try and sideload a rom with ADB to the directory that TWRP is reading from.
If you use Root Explorer and go to root(mount R/W), you can access your 'new' backups under data/media/TWRP. This is where I found all of my back ups after flashing a new ROM. This seems to be default storage for back ups, at least for me, so I copied my original stock back up form my 'sdcard' partition and brought it to the new location. That way I have an original configuration in both places; cover all the bases that way. Hopes this helps others......:good:
BTW - I am running EOS right now; not sure if this will be the case for every ROM flashed.......
Ok so I just rooted my S3, 4.4.2 Boost Mobile phone. Worked fine. No problem rooting it. Made a backup using CWM and then I installed Philz recovery and also made another back up. In recovery it shows BOTH backups, and says they are located in
/sdcard/clockworkmod/backup
then in individually named folders of the backups.
HOWEVER, when I look using ES File Explorer, I only have the clockworkmod folder, and it does NOT contain any other folders, no "backup" folder at all.
Ok, so let me try the Aroma File manager. Same thing if I go to /sdcard/0/clockworkmod/ there are two very small files:
".last_install_path", and ".recovery_version".
HOWEVER, I am able to navagate to /sdcard/clockworkmod/ and THERE I find the backup folder with my two backups.
Why can I not find this folder from android? Even when I use STORAGE ANALYZER and tell it to look at the system parttions and even when I use ES FILE MANAGER and tell it to do an SD CARD ANALYSIS, it doesn't show these backups. So I have copied a backup to the download folder of the sdcard and am hoping to copy it over to my PC before flashing a new ROM.
NOTE: I do NOT have an external SD Card installed yet.
I just thought this is super strange. ?? Anyone have any idea? Thanks.
Now after booting into Android and looking into the folder I copied to /Download, the folder is empty.. !?!? I'm SO LOST right now....
It SHOWS that space is missing on my device so these files DO EXIST SOMEWHERE but SOMEHOW it's as if they are being hidden... is it knox???
Ok if I use "MY FILES" I can see the folder that I copied to /Download and the files in it, but NOT if I use ES File Manager, and NOT if I use Root Explorer. However even MY FILES still shows clockworkmod dir as empty!?
Ok so it turns out it has something to do with a permissions issue. Why is that? I run Storage Analyzer and when I try to click on the recoveries I copied to /Download it tells me that I don't have permission for that folder. Do I need to run some kind of FIX PERMISSIONS on this? Is there such a thing for the S3?
I found someone else talking about this same thing and looks like they solved it. here is the link:
http://forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/229739-where-my-rom-manager-backups-android-4-2-a.html
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.
Hi everyone,
I'm going mad to find a way to replace my boot animation. Since I've installed the Pixel boot animation via Magisk, I've been no longer able to change it, via flashing or manually replacement. I've uninstalled of course the app that operated the last change to my boot animation before doing this operation. By trying the manually replacement my explorer says I can't delete, rename or move the bootanimation.zip because "It can't be remounted" or something like this. Does anyone know how to solve this problem?
Thanks in advance!
RegularSam said:
Hi everyone,
I'm going mad to find a way to replace my boot animation. Since I've installed the Pixel boot animation via Magisk, I've been no longer able to change it, via flashing or manually replacement. I've uninstalled of course the app that operated the last change to my boot animation before doing this operation. By trying the manually replacement my explorer says I can't delete, rename or move the bootanimation.zip because "It can't be remounted" or something like this. Does anyone know how to solve this problem?
Thanks in advance!
Click to expand...
Click to collapse
What file manager are you using? I use root explorer pro, it asks me if I want to re-mount the partition to read write then let's me do what I want with the file.
Sent from my [device_name] using XDA-Developers Legacy app
@RegularSam: if your filemanager is too lazy, use TWRP:
Mount system, then Advanced ..FileManager.
rp158 said:
@RegularSam: if your filemanager is too lazy, use TWRP:
Mount system, then Advanced ..FileManager.
Click to expand...
Click to collapse
I've tried with TWRP, replaced the boot animation.zip with the one I want but when I boot into the system it's like the old bootanimation from Magisk, for some reason, overwrite again the new, I've already tried twice. Any thoughts?
jd1639 said:
What file manager are you using? I use root explorer pro, it asks me if I want to re-mount the partition to read write then let's me do what I want with the file.
Click to expand...
Click to collapse
I use Solid Explorer, spent 3 euros to buy it so I have to make it work in some way lol. Anyway I'll make a try with Root Explorer.
Solved. Even if before all the changes I've deleted the module on Magisk, don't know why but in cache/magisk_mount there was still a sort of backup of the old bootanimation which was "reflashed" everytime some change to the media folder where made. Anyway, I simply renamed this file by adding .bak and flashed the bootanimation that I want, all from TWRP. In fact, another weird thing is that also Root Explorer can't handle this file, it gives in return the same problem of Solid Explorer, even by unmount e remount again. I can only touch these files from TWRP, don't know why.
RegularSam said:
Solved. Even if before all the changes I've deleted the module on Magisk, don't know why but in cache/magisk_mount there was still a sort of backup of the old bootanimation which was "reflashed" everytime some change to the media folder where made. Anyway, I simply renamed this file by adding .bak and flashed the bootanimation that I want, all from TWRP. In fact, another weird thing is that also Root Explorer can't handle this file, it gives in return the same problem of Solid Explorer, even by unmount e remount again. I can only touch these files from TWRP, don't know why.
Click to expand...
Click to collapse
Mate I'm suffering from the same problem if you can please elaborate on how did you renamed and flashed the file it would be highly helpful!
I wanted to update to the latest version of xiaomi.eu, which is no longer for fastboot, but for recovery. At first internal storage had (0mb), I changed it to EXT4, but still the problem is no visibility/ability to install the latest ROM copied to the phone, what to do?
I download the rom with the phone, reboot with TWRP-3.6.2, install, zip archive anb install, after select system an reboot
I cant do antything in TWRP because TWRP doesnt see ROM copied on storage.. All tutorials say "just go into twrp and install the copied rom", I don't see the copied ROM!
You have to look in a sub folder it will no show at root directory can't remember off hand might be data or meta something like that, after the OTA updater works great
Useing the Skkk latest TWRP by default it was in Chinese
jefffrom said:
You have to look in a sub folder it will no show at root directory can't remember off hand might be data or meta something like that, after the OTA updater works great
Click to expand...
Click to collapse
I dont have acces to /data foler "no such file or directory"
If you don't help yourself, no one here will.
1. TWRP installation
2. wipe+factory
3. boot system
4. copy rom
5. boot twrp
6. install