I trying to customize initramfs in stock Android Studio android-28 https://dl.google.com/android/repository/sys-img/android/x86_64-28_r04.zip I want to substitute SYSTEM partition to partition on sdcard. Unpacked ramdisk.img, put there /fstab.ranchu, /vendor/etc/fstab.ranchu and packed it back to ramdisk.img. The problem is that init does not see those files and loads in emulator as usual. >[ 1.196779] init: init first stage started!
>[ 1.197577] init: Using Android DT directory /sys/bus/platform/devices/ANDR0001:00/properties/android/
>[ 1.199700] init: [libfs_mgr]fs_mgr_read_fstab_default(): failed to find device default fstab
Full emulator init process https://pastebin.com/uXSY1CtS
I tried to build init program from stock.

repo init --depth=1 -u
https://android.googlesource.com/platform/manifest  -b android-10.0.0_r45
repo sync  --force-sync --no-clone-bundle --no-tags
source build/envsetup.sh
lunch aosp_x86_64-eng
cd system/core/init;     mm

I put init program back to ramdisk.img and got previous behavior. Here https://android.stackexchange.com/questions/217177/what-is-default-fstab-file-in-android written that fstab is in the proper place. And here is pease of code https://android.googlesource.com/platform/system/core/+/refs/tags/android-10.0.0_r3/fs_mgr/fs_mgr_fstab.cpp#445 about responsible fstab paths. **Edit:** i missed that Kernel command line: has skip_initramfs parameter according to https://pastebin.com/uXSY1CtS . So everything i tried to change in ramdisk.img was evoided. When i give special parameters to like that:

./emulator -avd test28 -no-cache -show-kernel -qemu -append "init=/init root=/dev/vda1"

It didn't solve the problem. Kernel still loads directly from root disk, ignoring ramdisk.img.

I'm trying to unpack Android 13/14 ROMs from a set of different vendors but it seems that all images using Android 13+ have some changes in how the filesystem images are built. Using simg2img (simg2img ./system.img ./system.raw) I'm capable of converting the sparse system.img file of a ROM correctly into some unknown image format. Inspecting the converted image shows that it no partition is detected. For Android version below 12 usually it was an ext4 partition.

file ./system.raw
./system.raw: data

However, the file command shows that it is recognized as a data partition. So I guessed that we need to identify some offset to be able to mount or convert this image correctly. I tried to identify if the partition is a F2FS image (following [this tutorial](https://baremetallics.com/blog/how-to-extract-f2fs-android-flash)) but wasn't successful in identifying the magic bytes for F2FS. Does anyone know how to mount or convert Android 13+ ROMs? Are there any good script out there to automate it?

Whenever I'm connecting my Samsung Galaxy A40 running Android 9.0 to a laptop or PC, I'm getting an annoying prompt to allow data transfer, and the following setting which I had set to "Charging phone only" gets reset to "Transferring files": However, I only want to charge the phone and absolutely never allow data transfer for security reasons as I frequently have to connect my phone to public or workplace PCs for charging. The service which throws the notification/prompt is called *Android System* and the icon looks a bit like this (only with filled font): I activated developer options and explicitly configured the USB connection settings to **not** allow data transfer. Why does *Android System* keep changing my settings and prompting for data transfer? Is this normal behaviour? Is there a way to regain control without having to root the device?

I am using Samsung Galaxy A50, Android 11, One UI 3.1. I use Samsung Secure folder. There are many bloatware in it and I could not find a way to uninstall (and disable) them via ADB. Owner profile user is 0, Secure Folder user is 150.

pm uninstall -k --user 150 com.android.chrome 

Exception occurred while executing 'uninstall': java.lang.SecurityException: Shell does not have permission to access user 150
com.android.server.am.ActivityManagerService.handleIncomingUser:17947 
android.app.ActivityManager.handleIncomingUser:4863 
com.android.server.pm.PackageManagerShellCommand.translateUserId:3125
    at com.android.server.am.UserController.handleIncomingUser(UserController.java:2375)
    at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:17947)
    at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:4863)
    at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:3125)
    at com.android.server.pm.PackageManagerShellCommand.runUninstall(PackageManagerShellCommand.java:2024)
    at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:237)
    at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
    at android.os.ShellCommand.exec(ShellCommand.java:44)
    at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:26662)
    at android.os.Binder.shellCommand(Binder.java:965)
    at android.os.Binder.onTransact(Binder.java:839)
    at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:5206)
    at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:5281)
    at android.os.Binder.execTransactInternal(Binder.java:1195)
    at android.os.Binder.execTransact(Binder.java:1159)

Where do I enter the commands for SU abilities and root access or settings? ``` fd = open("/system/file.txt", O_RDWR | O_LARGEFILE | O_NONBLOCK); if (fd Code source: https://android.stackexchange.com/q/213631 No, I'm not doing this for any reason, and I don't need to throw an explanation at all. I'm just tooling around and I'm trying to learn on my own as well as reading and doing my own research, so please spare me the whys, the whats, and the whos, and just explain to me where I enter these commands.

Some Android 5.0 users often complain about some system service constantly executing, so they just want to get rid of it *at any cost* to avoid battery drain. In my scenario, it's DreamManagerService which is unimportant right now. Since this is a system service (service list | grep -i dream), I can't find it in the process list (ps -x | grep -i dream), and interestingly also not seeing it in init.rc or similar.　This internal service is not listed anywhere in the app -- I've already investigated with the "disable service" app. So my question is more about: **how to stop a system service?** (specifically on Android) Note: it has been reported by other users that in Android 6, apparently, this service is visible and can be handled much better. --- As a short introduction (bonus FYI), the so-called DreamManagerService , namely DayDreams or simply screensaver, makes sense for OLED screens, which turn off black pixels, but some LCD IPS phones also allow this functionality (unreasonably). Obviously, I have already checked that the configuration is okay (disable screensaver ), but the service is still running and somehow preventing the CPU from sleeping, thus eating up the battery. This fact can be diagnosed by using the Wakelock Detector app or a similar one.

Applications on Android use class android.util.Log for producing logging output with log level, tag etc. We can view the logs using tool logcat. Writing to standard error output also writes to the same log, but with tag System.err. I am wondering how this works internally. Does each application have open some file descriptor to a pipe or socket, which has the “log processing stuff” attached on the other end? When looking to the source code of the android.util.Log class, I see that the messages end up in some native function: /** * Low-level logging call. * @param bufID The buffer ID to receive the message. * @param priority The priority of the message. * @param tag Used to identify the source of a log message. It usually identifies * the class or activity where the log call occurs. * @param msg The message you would like logged. * @return A positive value if the message was loggable (see {@link #isLoggable}). * @hide */ @UnsupportedAppUsage public static native int println_native(int bufID, int priority, String tag, String msg); I also noticed that some of the log can become lost (not flushed) when the process of the app exits directly, using java.lang.System.exit, but the stderr output is not lost. What does this function do? I ask only for educational purposes and I know that the portable way of logging is to use proper Android SDK/NDK functions.

How can I mount the /system directory rewritable or read-only on my Android phone?

Important things: 1. Termux binaries are in /data/data/com.termux/files/usr/bin 2. Termux libraries are in /data/data/com.termux/files/usr/lib 3. Android binaries are in /system/bin 4. Android libraries are (mostly) in /system/lib64 I am trying to execute termux binaries from a root shell (on a rooted phone, after a successful "su" command). Most of them work, although they are not in the PATH. On ordinary Linuxes, the environment variable LD_LIBRARY_PATH could do the trick. However, the so-named "ordinary linuxes" are mostly open source linux distributions based on the GNU Libc, which has a dynamic linker (named "ld.so"), which can interpret it. However, Android binaries are using another libc, and another linker. My tests show it is in /system/bin/linker64 and it does not honor LD_LIBRARY_PATH. So, how could I execute termux tools from a root shell, which they can find /data/data/com.termux/files/usr/lib if needed?

I am interested in learning how to write to (and if possible, read from) a rooted Android device's clipboard. I hope to do so using ADB over USB and I am not interested in installing any apps to help me do this, as this is something I plan on rarely doing. Any suggestions or help guiding me in the right direction would be greatly appreciated.

No app blockers works as I can go into safe mode and delete the app blockers. How do I tune my Samsung Galaxy S24 enough to not have an option to go into safe mode altogether?

I have a Xiaomi Mi A2 running Android Ice Cold Project (AICP) nightly build 15.0 (Android 10). I don't know what I did, but after installing a custom ROM, I noticed that my system partition cannot be mounted as read/write. I tried 1. mount -o rw,remount /system command on a terminal emulator, ADB shell, and TWRP terminal. The command shows no feedback showing failure (maybe I succeeded?) 2. Mount it using the built-in TWRP mount function. The system check box can be checked out (it doesn't retain its check mark on reboot) Some apps actually work according to sources and reviews. Some say (Failure to mount..), some say (System mounted as rw), and some don't have feedback. I don't know what to do. I noticed this when I installed a custom ROM. I tried using another custom ROM but same thing. Also, reformatting doesn't help. I don't know if this occurs on the stock ROM.

I was trying to access my /obb and /data folders in my Samsung Galaxy M33 5G, but because of restrictions in Android 14, I was not allowed to do so, somehow I found out this. I checked that whenever you update your Google Play system update, your Files app gets updated, I uninstalled the update and I got it in the apps screen, and I could finally access these restricted folders without any 3rd-party applications or something. [Video demonstration on Google Drive](https://drive.google.com/file/d/1AG-Dn9olqawLht2HVjuTlp39EA4pvSUV/view?usp=sharing) . I found many solutions on YouTube, but each of them involved 3rd party apps. Is it a bug that I can access them?

I have a rooted Android 13 device with dm-verity disabled. How can I remount the system partition for read and write permission without Magisk installed?

I am looking for the files that correspond to the recorded fingerprints on my Nexus 6P and a way to "reset" the fingerprint system. Something similar to how Android stores lock screen settings (pattern etc.) under /data/system/locksettings.db*, and you can remove the lock screen by deleting these files (if you have root access). The reason I am asking is because after a TWRP restore on a new Nexus 6P, my fingerprint hardware is not working anymore. The error message is **Fingerprint hardware not available**. Also see this question: https://android.stackexchange.com/questions/146010/fingerprint-hardware-not-available-after-twrp-restore All five previously recorded fingerprints show up on the settings UI, but I am not able to delete them by clicking "Delete".

The app/process "system updates" started using network data constantly a few days ago, also I think the battery is drained faster. Should I be worried about being hacked, or is this just some bug? And how do I make this stop? I'm using crDroid 9.0 (android 13) ROM (from here , I think) on Samsung S8. The first screenshot from android settings shows data usage in about 3 days. And the second screenshot from PCAPdroid app shows data usage in a few minutes, to see the IP adresses it connects to. Seems the IPs belong to google. Also, I think my phone is identified as pixel phone by google, maybe this has something to do with this, maybe google tries to update this "pixel phone".. But what seems weird is the data speed, which is always only a few KB/s, if google only tried to download pixel update files, I would think it could reach higher speeds.

I need to "downgrade" the google app with an older version because of a voice typing issue. However, the older version gets uninstalled after reboot. I have explicitly uninstall the original one then install the one I want, but after reboot, it's reverted back. I Know system app can be restored, thus an apk is probably resides in the system image partition. If I only disable/uninstall the google app, then it stays "gone" after reboot. So I need to disable the auto-update on system app if possible. Or replace the original with the older version in the corresponding partitions.

I bought two Android tablets which supposedly came with Android 12, 16GB of memory, and 1TB of storage. Unfortunately, when I started adding apps and videos, it soon ran out of space. I followed a solution on the forum, installed F-Droid, Termux, and ran it, which informed me that the tablets are Android 8, 16GB RAM, and 32GB of storage. Is there any way I can de-fake them and show the correct attributes?

When I install an application, in most cases it is smaller than the file downloaded from the play store, I checked these applications in /data/app and it turned out that all applications that use the Incremental File System have this error, if the application uses f2fs, it displays normal (150 mb) otherwise only 32 mb is displayed. It seems that most of the applications installed by the main user from the play store install to the Incremental File System, when I install the same application but first on the second user and then on the main one, then the file system is f2fs Original post: ------------- The size of the application in the settings is smaller than the one downloaded from the play store and also when leaving and entering the settings the size of the application keeps decreasing, for example in the play store the application weighs 90 mb, we install it, it weighs only 70 mb, we open the settings a few more times and this size drops to only 30 mb. Why does this happen? In my opinion, the size of the application should be rather constant and only the data and temporary memory can change. I'm not 100% sure, but this problem happened to me on Coloros phones and derivatives, e.g. realme ui. Video https://imgur.com/a/p4zqHGt Edit 1 log: https://gist.github.com/432533/e53c8fa441636aa0daec60d3245afef6 the package name of the application I used as an example is com.lastquarterstudios.catsareliquidabp Information Update: ------------------- I found out that the error occurs only when I install the application for the main user (userid 0) from the play store, when I install the application on another user, the size is displayed correctly 150 mb. When I install the apk, xapk, apkm file, the error does not occur. When I install the same application first on the second user, e.g. userid 13 and then install it with play store on the main user, the displayed size of the application is normal. I am not sure, but when I download the application update from the Play Store, the application originally installed on the main user (userid 0) is fixed. I managed to notice the error on 3 phones, on my oppo, realme and my friend's realme, and I determined that the bug probably exists since android 12. Just to clarify, if the translation is not accurate, the error occurs for all installed applications, mostly games, among applications it also happens but less often, I'm not 100% sure. Log: - Running the same application on 2 different phones https://gist.github.com/432533/998c09294576d96c408cb951cde808ed realme https://gist.github.com/432533/206bca657c4f9adab99512453077df64 oppo - Checking the size of the application that was first installed on the second user and then on the main user https://gist.github.com/432533/c20b00fee6eca4a941136c28418b5cb9 (coloros 12) - Installation process from the Play Store on the device with an error https://gist.github.com/432533/872d7441270f2b2163bacde0a063b410

I am using Magisk 20.4 and trying to mount /system on a Google Pixel (1st gen) running Android 10. I have tried using: adb shell su -c mount -o rw,remount /system that gives: > mount: '/system' not in /proc/mounts The following also do not work: adb shell su -c mount -o rw,remount / > '/dev/root' is read-only adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root > '/sbin/.magisk/block/system_root' is read-only I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case.. Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel? Cheers, Paschalis #### Trying Hack5 suggestion gives me: > mount: '/system' not in /proc/mounts Since I knew that /sbin/.magisk/mirror/system_root was a valid mount point, Ive tried the following, which still fails: mount -wo remount /dev/block/bootdevice/by-name/system$(getprop ro.boot.slot_suffix) /sbin/.magisk/block/system_root > mount: '/sbin/.magisk/block/system_root' not in /proc/mounts # UPDATE: Turns out it's impossible to mount /system on a factory image of Google Pixel. But, I was missing the whole point of Magisk! So I made a few modules and I can override/add the system libs and bins that I need. There is even support for apex on Android 10!