Related
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!!
I keep trying to edit build.prop on my 5x as I've done on previous devices in the past. Going through file explorers setting it to Rw doesn't actually change it. Does anyone know how to actually set it as rw so it can be modified? I'm trying to add eis, if anyone else has tried.
Thanks!
Atemi1337 said:
I keep trying to edit build.prop on my 5x as I've done on previous devices in the past. Going through file explorers setting it to Rw doesn't actually change it. Does anyone know how to actually set it as rw so it can be modified? I'm trying to add eis, if anyone else has tried.
Thanks!
Click to expand...
Click to collapse
are you sure you are properly rooted? what method did you use?
do other root apps work as intended, which file explorers are you talking about, are you on stock?
just asking, since there are root procedures around through which you funnily enough end up with a r/o rooted device. also the more relevant information you give, the easier it is to help.
Broken303 said:
are you sure you are properly rooted? what method did you use?
do other root apps work as intended, which file explorers are you talking about, are you on stock?
just asking, since there are root procedures around through which you funnily enough end up with a r/o rooted device. also the more relevant information you give, the easier it is to help.
Click to expand...
Click to collapse
I followed a guide in November, don't remember which. All done through adb. All root apps work fine, xposed, titanium Backup, etc. I've tried stock, es file explorer and FX file explorer. Also for giggles I tried Rom Toolbox Pro. Also, in twrp it does say I'm not encrypted.
When trying to edit the file, it only gives me a cannot modify file error.
Atemi1337 said:
I followed a guide in November, don't remember which. All done through adb. All root apps work fine, xposed, titanium Backup, etc. I've tried stock, es file explorer and FX file explorer. Also for giggles I tried Rom Toolbox Pro. Also, in twrp it does say I'm not encrypted.
When trying to edit the file, it only gives me a cannot modify file error.
Click to expand...
Click to collapse
Did you mount system rw before trying to edit the file?
In ES it's under Tools > turn root explorer on, then tap it and mount rw
Same for me...
berndblb said:
Did you mount system rw before trying to edit the file?
In ES it's under Tools > turn root explorer on, then tap it and mount rw
Click to expand...
Click to collapse
Using ES worked perfectly. No other actually worked. Many thanks!
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
lawtalking said:
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
Click to expand...
Click to collapse
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
lucky_strike33 said:
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
Click to expand...
Click to collapse
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
lawtalking said:
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
Click to expand...
Click to collapse
What file explorer are you using. Fx works fine.
toknitup420 said:
What file explorer are you using. Fx works fine.
Click to expand...
Click to collapse
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
lawtalking said:
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
Click to expand...
Click to collapse
You may have a SUPER.img - i just learned about this myself - its a combined image containing /system - /vendor & /Product - it looks like it is similar to Systemless root or system as root... idk they are weird but i do think its possible to modify build.rpop, but it may require a PC.... Im looking for a way to edit build.prop myself and learning all this now.
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!
Hi, I need to give read and write access to a couple little files in my root directory, but I can't find a file manager app that will do this. Among the ones I have tried are Root Explorer, which was recommended, and File Manager Root from Fdroid, but neither work. Can someone recommend an app or another way to do this? Thanks!
reidun76 said:
Hi, I need to give read and write access to a couple little files in my root directory, but I can't find a file manager app that will do this. Among the ones I have tried are Root Explorer, which was recommended, and File Manager Root from Fdroid, but neither work. Can someone recommend an app or another way to do this? Thanks!
Click to expand...
Click to collapse
In modern android versions the /system partition is read only. Either you create an overlay with magisk, or you boot recovery. Twrp has a file manager or you use adb shell.