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 have a Xiaomi Mi 6X which is the Chinese version of A2. There is a way to convert it into A2, but OTA updates won't work because 6X has only A partition. I'm not sure, but I've read, it is possible to create/delete partitions on an Android device. So I want to create A/B partitions manually, but I have no idea how it looks like.

I am trying to root my Mi A2 android phone. I am following this tutorial. When I try fastboot boot path/to/twrp/image the phone gets stuck on the boot screen. What am I doing wrong? Is it because a) I don't have required drivers or because b) I have to disable force encryption? If a) I have to install new drivers what are they, where do I get them and how do I install them? If it is b) about disabling force encryption then how to do it?

In the offitical installation instructions for Magisk it says: “However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN” *What’s the rationale for having the stock boot image dump beforehand?* If the rationale is to have a backup when something goes wrong, then strictly having a stock boot image dump is not necessary for running Magisk. Furthermore, it is unclear to me how to create that dump. PS: My plan is to root the Xiaomi A2, to be able to directly interface with USB OTG devices from within Termux . The Xiaomi A2 is an Android One device.

My Mi A2 recently started switching on its bluetooth automatically, and I set a stopwatch to count the minutes and it switches on after every 5 minutes dot on the clock. Please could ya help me out ASAP?

Is there any way to disable the Alt+Tab shortcut when using physical keyboard on android phone ,I'm using xiaomi Mi a2 phone.

I'm trying to flash TWRP Recovery into my Mi A2 recovery. However I get the error when flashing: ~$ fastboot flash recovery twrp.img FAILED (remote: '(recovery_a) No such partition') Does anyone know how to fix this error? I did test flashing it to boot_b, and that did work. but that's not the recovery slot.

Yesterday I took my Xiaomi Mi A2 from my pocket and saw a warning screen (text-only) telling me the device couldnt start and if the issue persisted I might need to do a factory reset and wipe all my data. I clicked try again. After starting, my device displays an error message - "process com.android.phone stopped". When I try to unlock the phone it starts rebooting after a few seconds. When I slide down the top tool bar the device also starts to reboot. I searched for a solution but didn't find a fix that works for me. Some of the suggestions relating to a simmilar issue (but the error message in those cases starts with "Unfortunately" and the devices seem to be somewhat servicable) suggest wiping cache, contacts or SIM tools but all of those are inaccessible to me because the device reboots all the time. Another solution for wiping the cache is using adb command line tool. But adb doesn't "see" devices without USB debugging enabled - which again I can't enable because I cannot access the settings menu (reboots). fastboot seems to be able to delete cache with fastboot erase cache but I'm prevented from doing this because of an error - FAILED (remote: 'Erase is not allowed in Lock State'). I'm not sure if this Lock State gets unlocked with fastboot oem unlock but from what I understand that would wipe my device anyway. Finding all of this out took quite some time so at this point I don't know what else to do as I have very little knowledge about this area. Is there any way to at least attempt to clean the cache or will I have to go for the factory reset? I'm not entirely sure if I have all the Google Authenticator recovery codes so I'm hesitant to do so. I've had an old iPhone 4 for some 4 years and I've never had to invest so much time into that so you can imagine why this frustrates me at this point.