Question Advice (what do you not know?) - Redmi Note 10

I can't change the system files.
I have root privileges and also root file manager.
At most it will let me delete a file, but I can't add another one.
Even TWRP recovery won't let me do that.
I only noticed this problem here on Android 11.
On Android 10 (even on the A/B system) I still managed.
Does anyone have a proven working procedure?

I noticed that many file managers have problems reading and modifying files on /system partition since Android 11 update.
for instance Solid Explorer is showing corrupt filenames in /system, is unable to change files. The same with other root file explorers.
SOME filemanagers however seem to be working, like X-plorer and maybe in your case Total Commander (i didn't test). maybe they have been updated recently for some changes in Android 11 filesystem, or were built to handle it correctly from the beginning.
This is defenitely something that needs to be fixed on file explorer apps sides.
some more information https://android.stackexchange.com/q...t-see-contents-of-android-data-even-with-root

It's true. With the advent of Android 11, we need to get the file managers updated with the new environment.
So far my favorite thing to use is Root Explorer, and I also had to update it to the current version. It can then handle the new environment. Total Commander is similar.
EDIT: Appearances are deceiving. Even the latest versions of these tools won't actually insert a file into the system, at least not a working one. They can only create an empty file. So it's true that I don't know how to use it yet.

After further testing, I haven't found a file manager that has no problem adding anything to the system.
Even the X-plore didn't help.
The problem is not in the rights, but in the fact that the system folders show 0 free bytes!
So there is nowhere to store the data.

hm when there is 0 bytes free I think it's actually read-only (super)partition. it's still kinda tricky to handle things like this on A11.
what about: enable USB debugging + USB root debugging and then: adb push /system/stuff?

We have to try different ones. But as I wrote, it's not a rights issue. I copy the file to the system, but then it has size 0b and is empty.

File Manager on F-droid (com.github.axet.filemanager) seems to be very lightweight but functional root explorer. give it a try. maybe it works better than others. at least I could browse root stuff correctly

Related

Why do programs with root not see past the data folder?

Hey all, I'm a noob. But I got my NT pretty much where I want it to be. I realize now that the extra space is in the data file system (yeah, I can use the extra gigs). Now, my biggest problem is that my .cbz .cbr files do not have a default program or association. This is a problem because my root accessible comic readers will read to the data folder but when you open up the data folder it says nothing is there. At this point, I just need a comic app that links up .cbz .cbr s as the default program for those file types so that I can open the file from on of my file expolorer programs. Or I need to figure out a way that allows my rooted comic apps to actually go into the data folder. Why won't these programs look into the file system past data?
Now,
I did try the permanence method to link a usrdata file to the mnt/internal file, but while it creates the mnt/internal file it does not fill it in with my files...which sucks (I just folled the instructions and I think it may require the snowball mod). I do like the B&N reader for my epubs, so I don't want to use the snowball mod
And even in snowball could not work, in OP is posted that many apps can still be incompatible
Sent from XDA using one of my Android Toys

Lost access to media - ringtones, alarms, notifications and other media files

I have also posted this issue on another general forum, so apologies if this is deemed cross-posting!
My smartphone is running a stock Lollipop C6833_14.5.A.0.242_Customzied Germany.ftf ROM flashed using Flashtool, but is rooted with KingRoot and I have a dual recovery flashed and working properly.
Following that downgrade I found that my phone no longer had either a phone or alarm tone. When I try and change the alarm tone or ringtone or even notifications in settings I am presented with the file explorer. The sound selector shows nothing. File Commander is able to see and access the files, and they do not appear to be corrupted and I also tested them in my media player.
They were not in the SD card media folder, but were in tact in the system/media/audio folder in their respective folders. So I copied all the individual folders within the audio folder across to the corresponding media folder on the SD card. But that did not work either...
After searching various sites for help I managed to find instructions to download and flash Xperia Lollipop Media Sounds.zip, which I tried to do with TWRP recovery, but this failed with an error message I could not read.
I wondered whether if I were to just flash the system file from the same ROM it would restore the media file settings? Any help would be very much appreciated, as I have no way of hearing when I receive incoming calls, and my alarm does not work either. The audio seems to function fine in third party apps, so there is no physical issue as far as I know.
I also read a recommendation to copy the files across while connected to a PC, via USB, but my computer is a Mac and it does not seem to be able to access the SD cards as external drives in the same way as they appear in a PC.
Sony technical support basically told me that the only solution is to use repair within the Sony Bridge for Mac app, but I don't want to lose root, as the latest firmware upgrade is impossible to root. I really need help on this please!
Be aware that you have to set the correct file permissions after moving them to the /audio folder. The ringtones and alarm tones should be in the folder you just wrote, meaning they're on the system partition.
Just long-press or something on the audio-folder (depending on the file explorer you're using), tap "properties", and then set the permissions to 6-4-4, which is RW-R-R, or:
[x] [x] [ ]
[x] [ ] [ ]
[x] [ ] [ ]
Then reboot.
Hi Klaoss, many thanks for replying. However I have checked the permissions. The permissions for the actual files are RW-R-R, but in fact the folder permissions seem to be even more open: drwxr-xr-x, does that sound correct? I am talking about/system/media/audio/alarms, camera, notifications, ringtones and ui, which all have the same permissions.
Uh Oh! I just checked the permissions in the /storage/emulated/0/media/audio folder are non existent! Maybe this is why it is necessary to use the PC to copy the files, in order to retain the file and folder permissions? Is it also something to do with the actual formatting of the SD partition? Thanks for your patience
Just checked mine (on 5.1.1) and it does indeed look like the folders are drwxr-xr-x, while the files themselves are rw-r-r.
Also, yeah you could try that. That might actually work. Just remember to reboot after each change.
Thanks, but to be clear, do the files need to also be in /storage/emulated/0/media/ as well as in the /system/media/audio, or are they superfluous? Because if they are not needed, then I am not going to achieve anything by going to the trouble of copying the files within a PC environment.
Also, is there no way of copying files within Android without losing the permissions?
No idea, but I've always added and removed audio files from the system partition, but I know apps like Zedge and stuff adds them to the list when downloaded, so I'm guessing that 3rd party apps use the media folder on the internal memory, and not on the system partition, which requires root. So I would probably just let that folder alone, and concentrate on the system folder. Check the permissions and see what happens.
Change the permission on one or two files (incl. the folder), reboot and see if the file/files you just edited are showing up in the ringtone list. If yes, then change the permissions on the rest of them.
I have no idea what to change the system folder permissions to...remember that they were set to drwxr-xr-x. I think it is more important to be able to provide access to third party apps, that way I could temporarily choose ringtones etc using those. However I cannot access the permissions for the folder of the internal memory via my file explorer apps, even with full root access. That has to be a contributory factor to the problem. I wonder, would you mind having a look at the permissions for these folders on your device and telling me what they are compared to the system version?
Also, I would like someone else's take on this, would anyone else care to comment please?
OK, same problem, different tack: can anyone please tell me which partition I would need to reflash from a ROM or TWRP backup to restore the system media sounds and settings to original without losing my data or root? Also does it need to be the same ROM version, or can I flash a different ROM, but still a version of Lollipop? For example, could I simply extract the relevant partition from the recent 5.1.1. ROM, or would I then lose root too, or could it come from a 5.0.1 ROM, but slightly different from the one presently installed? I have several TWRP backups, but unfortunately for some reason they included the TA information (ta.mmc.win) which causes a bootloop when I try and reboot the system after flashing, and I have yet to find a way to exclude them from the restore process.

Unable to find CWM backup after fail

I know we’ve seen variations on this question, but my issue is a bit different, and none of what I can find has been able to help me.
I was doing a backup straight through CWM, when it failed towards the end and I can’t seem to find it anywhere, and I’m left with only 32m of space. I’m using ES File Explorer, I’ve been to all of the suggested locations, but I’m simply not finding it. I can’t find a Clockworkmod directory at all – even doing a full on search from the root directory.
I went back to CWM’s advanced backup feature and it lists it, so I know it’s “there”.
I’ve cleaned the caches and my space is still sapped.
One thing I have noticed is that ES File Explorer isn’t requesting superuser privileges, but it can still see the root. Is it in some hidden directory and I’m just not able to get it because of the superuser thing?
And something else that might be an issue. I’ve got SDCard\0\0\0\0\0 But I’ve been through each of them in the “Media” directories and have not found it. (That whole nested 0 thing is another question I’ll be posting tonight.)
Thanks for any help on this.
I solved the problem. My stupidity was to blame. Didn't realize that ES file explorer's options were scrollable past "Settings". Found the view hidden files option there.

ADB functions clarification and usage for data transfer/backup on an image disk

Hello xda-developers,
I'm trying to figure out the proper way to transfer app data from an Android image disk. I'm very new to this, so I hope I'm not missing something basic.
Situation. I have a .img disk image file obtained from a .vmdk file via a virtualbox conversion , the latter being created by an Android emulator. I'm trying to recover some app data and transfer that to a new, working, .img disk. The emulator works on Android 4.4.2, if that matters.
What I did. I extracted apks and copied app data folders (com.<devname>.<appname>) from/to the /data/data directory. I did that using a file manager (ES file explorer) or via the cp command, as I found in many tutorials and guides. Others suggested to copy those folders to /Android/data instead, so I did try that as well. These procedures were ineffective, because they both messed up with folders and files permissions. Although cp -ar retains folders/files permissions and ownership, that was of no use after the import into the working image. Those operations were performed on Ubuntu 18.04.
The problem (and a workaround). When the apks are installed, a new uid (in the 10000 group) is generated for them. These values are unknown when I import the data folders, hence they are destroyed at phone boot. A log in /data/system/uiderrors.txt confirms this. The only way I could make it work was to install the apk from scratch, open the app so that the new data folders are created with a proper uid, replace those folders with old ones and manually change ownership and permissions accordingly (for every apk). This turned out to be effective but it's a very tedious and error-prone process.
What am I doing wrong? How do ADB push, pull and backup commands manage folders permissions/ownership and app uids? Could they be useful in my situation? If so, how can I use them on a .img file?
Thank you.

Rooted device (No.1 D5+) rename / delete boot melody file

Hi,
I own a No.1 D5+ (smart watch - runs a standard Android 5.1, not Android Wear). The watch works well enough for what I had in mind when buying it, but there is one annoying thing: during bootup and shutdown it plays a melody at full volume regardless of the volume settings.
My plan was to root the device and delete / replace the file containing the melody. I searched for instructions specific to my model but couldn't find much, so I tried my luck with Kingoroot. That seems to have worked, though the root explorer app installed during the process still says it's not rooted, contrary to what the Kingoroot says.
Anyway, I tried renaming / deleting / overwriting the file both through Android Studio's Device Explorer and via adb shell, but always get an error "remote Read-only file system".
I'm guessing that means the /system/ folder is in ROM and can't be changed, or could it still be a software write protection? Is there anything else I could try to silence booting/shutting down?
I'm pretty new to all this, so any help is appreciated!

Categories

Resources