text:
Howto downgrade any app to the previous version without losing data on android oreo?
Howto downgrade any app to the previous version without losing data on android 8.1 ?
EDIT 0 : Nota Bene : Here, Fairemail is given as an example, my question is not app specific but Android specific. I'm actually asking how to downgrade any app to it's previous release having already downloaded the apk.
Here is the information of the package eu.faircode.email I want to push to downgrade :

$ du -h eu.faircode.email_1036.apk
13M eu.faircode.email_1036.apk
$ aapt2 dump badging eu.faircode.email_1036.apk | egrep '^$|package|[s]dkVersion:|application-label:|native-code:'
package: name='eu.faircode.email' versionCode='1036' versionName='1.1036' platformBuildVersionName='' platformBuildVersionCode='' compileSdkVersion='29' compileSdkVersionCodename='10'
sdkVersion:'21'
application-label:'FairEmail'
native-code: 'arm64-v8a' 'armeabi-v7a' 'x86' 'x86_64'

I tried to reinstall this app without data-loss :
$ adb install -r -d eu.faircode.email_1036.apk
Performing Streamed Install
adb: failed to install eu.faircode.email_1036.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

but it didn't work, so I tried the un-installation of this app without data loss and it worked :
$ adb uninstall -k eu.faircode.email
The -k option uninstalls the application while retaining the data/cache.
At the moment, there is no way to remove the remaining data.
You will have to reinstall the application with the same signature, and fully uninstall it.
If you truly wish to continue, execute 'adb shell cmd package uninstall -k'.
$ adb shell cmd package uninstall -k eu.faircode.email
Success

But then the installation of eu.faircode.email_1036.apk didn't :
$ adb install eu.faircode.email_1036.apk
Performing Streamed Install
adb: failed to install eu.faircode.email_1036.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]
$ adb install -d eu.faircode.email_1036.apk
Performing Streamed Install
adb: failed to install eu.faircode.email_1036.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]
$ echo $?
1

It seems adb install -d is only use-able with debuggable packages only according to this :
$ adb | grep downgrade
      -d: allow version code downgrade (debuggable packages only)

Can you help me ?

For me, using Termux, I could downgrade connectbot using cmd package install -d my.apk -- see also https://github.com/connectbot/connectbot/issues/1031. Presumably this package has debugging enabled? The command simply reported Success after a few seconds and the app worked again on my device.

What you want is not possible and for a good reason: updated data structures (files, database, etc) are often incompatible with old app versions. This is why you can downgrade debuggable packages (for development purposes) only.
If you have a problem with FairEmail, please report it in this forum:
https://forum.xda-developers.com/android/apps-games/source-email-t3824168

@M66B Last I downgraded another app because it was crashing on my device. This question is not app specific. I'm actually asking how to downgrade any app to it's previous version having already downloaded the apk.

@SebMa the answer was intended to be generic, but I was not sure if the question was general, hence the link to the FairEmail forum

I understand the risk. Although I'm not sure developers bother update their data structures every now and then, otherwise they will have to rewrite their I/O components often.

@SebMa especially when using Android ROOM it is easy to add new fields for new features to an existing database, so this might happen more than you think.

If your device is rooted, there's a work-around (apply at your own risk – as Marcel correctly pointed out, there's a reason why it's made close to impossible):

install titanium-backup
backup the app you want to downgrade
uninstall the app you want to downgrade (completely, i.e. app & data)
install the older version
use Titanium Backup to restore data only

This worked for me in several cases. No guarantees however: if the newer version changed structures in its databases/configuration, you will end up with an unstable app – and later updates might fail (in those cases, use TiBu to restore the full backup you made originally – so make sure to keep that one safe).

The pb. is that my device is not rooted. I've read about this, have you tried it ?

Also *migration mode * in settings may be needed to ensure DB integrity

@SebMa Yes, I have – and am quite happy with it. TiBu works fine on Magisk (to my experience on multiple devices, you can safely ignore TiBu's warning concerning SuperUser in that configuration).

Nokia TA-1041, android 8.0.0.
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
Ubuntu 20.04.3 LTS x86_64
Kernel: 5.13.0-40-generic
I actually met a similar problem, when downgrading the WeChat from 8.0.18 to 7.0.21. I tried adb install -r -d and adb install -r -t -d, both of them does not work, with the error [INSTALL_FAILED_VERSION_DOWNGRADE].
However, I tried this method, it works. https://moreless.medium.com/how-to-downgrade-an-android-app-without-losing-chat-history-afea00141601

adb shell cmd package uninstall -k <package>  to uninstall package.
adb reboot to reboot your phone.
adb install <package_apk_file.apk>  to install a lower version app.

Note that the reboot is very important, this step could not be avoided. I actually tried adb shell cmd package uninstall -k before reading the page above. But as long as I do not reboot, the lower version could not be installed, with the error [INSTALL_FAILED_VERSION_DOWNGRADE].

Additionally, https://blog.csdn.net/u012852597/article/details/108814434 from this article, it seems that you could also try to copy the apk file to '/data/local/tmp/' and install the apk.

Your answer basically just links to medium.com where the actual solution is described which is bad style for answers as linked web pages can change at any time or the link goes dead which makes your answer useless. Please always include the relevant steps for solving the problem.

Modified. Is it good now?


text:
Enabling Multi User Feature on Realme 3
Can anybody help me with enabling the multiple user feature like stock Android without rooting. I've tried getting the default.prop through adb and changing some properties and then replacing the copy on the phone with that but it wouldn't let me, cause my phone is not rooted and it's telling that I don't have permission. I don't wanna try rooting the phone just yet, cause it's a relatively new unit.So there's probably no stable root guide for it yet and so I don't wanna accidentally hard brick my phone.
Please somebody help me with this.If you have any suggestions and thank you in advance.

Multi-user feature must be enabled in Android framework while building ROM: https://source.android.com/devices/tech/admin/multi-user#applying_the_overlay. If the OEM/ROM developer didn't, you need to modify framework-res.apk file at least which is not possible without root.

No, multi user feature is not available in Realme 3 containing Coloros 6.And you cannot enable it without rooting. Realme 3 is based on Mediatek chipset, so you will not get good support for third party ROMs. But in future this phone will get RealmeUI update, which may bring multi user feature.

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

sort: votes


text:
Removing white transparent space caused by Google Search Bar on the home screen after disabling Google app
I would like to know how to remove this artifact of the Google Search Bar after disabling the Google app.

Possibly there is a search bar toggle in settings somewhere?

Change the launcher app. Some stock launcher apps don't allow removing the Google search widget.

What happens if you long press on it?

think changing the launcher app may be key to removing this bar

That's the Google Search widget, but since you disabled it, it looks like a gray bar.
Just long press on it then you should be able to remove it as you would do with other widgets.
Check this video out on how to do it: https://youtu.be/Vn07c-5XcdM

this is not a normal widget because a long-press has no effect even after re-enabling the search function

I have never encountered such issue. I am not sure to be honest

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
No full disk encryption in Samsung Galaxy A71
I just started using my brand new Samsung Galaxy A71 (Android version 10) by doing an initial setup, and it seems it does not support full disk encryption at all. On the contrary, on Samsung Galaxy A7 it was pretty easy to enable it. As it is impossible that in 2020 mobile devices without encryption being sold, I have done a google-fu, and, weirdly, there is no indication that anyone already searched for this feature.
Where is this function hidden then?

Your phone launched with Android 10.
In Android 10 Full Disk Encryption has been dropped in favor of File Based Encryption
You no longer need to "encrypt a disk" as everything is encrypted provided you have a lock screen with pin/fingerprint/etc. in Android 10

Thank you! It makes sense, and now I feel stupid for not checking the official documentation itself. The answer is accepted after reading the linked pages. Thank you very much once again!


text:
Music stops when the screen is off
After selecting a music file to open in file explorer in a floating mode, the music stops as soon as the phone is locked. I whitelisted both the player and explorer in battery saver settings but no luck. Playing music in the music player itself isn't creating this problem, though.

(Click to enlarge)
Edit: The device is Redmi 5 plus but it's on a custom rom (Havoc OS 3.3, Android Q). The music player is Hash Music Player

Could you reclarify on "playing music in the music player itself isn't creating this problem"? Did you mean the issue only occurs when playing music from file explorer, but not if directly from the player? Also, each music player has different behavior, so more details (as asked above) will help us more in finding the solution.

@AndrewT. I wanted to say that playing songs directly from the player doesn't create this problem. But when I open an audio file from explorer with a floating screen (see the screenshot above), the (floating) player stops working when the phone gets locked. I added more information in the edit above.

I don't think screen off/on has any bearing on this app. I installed the app, played the music from stock file manager. But the moment I switched to an another app music stopped. It is likely the app is not creating a background service (I didn't verify though) to continue the playback when its activity (that floating window) is destroyed.


text:
Downloading file using wget in Termux fails due to the character '&' in the URL
When I simply put this URL in my Android Chrome or any web browser:
https://api.worldtradingdata.com/api/v1/stock?symbol=AHT.L,AZN.L,AUTO.L,AVV.L,AV.L&api_token=39W3kqXKo1zm04k5De0yutk7iNtEKygnYPqDTowXy94EwgBUNAb3yY3XHHbN&output=csv

I get the file: worldtradingdata-realtimeprices.csv
But when I put this in Termux:
wget -O /storage/emulated/0/Download/worldtradingdata-realtimeprices.csv https://api.worldtradingdata.com/api/v1/stock?symbol=AHT.L,AZN.L,AUTO.L,AVV.L,AV.L&api_token=39W3kqXKo1zm04k5De0yutk7iNtEKygnYPqDTowXy94EwgBUNAb3yY3XHHbN&output=csv/worldtradingdata-realtimeprices.csv

I get this instead
Redirecting output to ‘wget-log.2’.

When I press enter, I get
[1]- Done wget -O /storage/emulated/0/Download/worldtradingdata-realtimeprices.csv https://api.worldtradingdata.com/api/v1/stock?symbol=AHT.L,AZN.L,AUTO.L,AVV.L,AV.L [2]+ Done api_token=39W3kqXKo1zm04k5De0yutk7iNtEKygnYPqDTowXy94EwgBUNAb3yY3XHHbN $

It breaks where "&" comes in my URL after AV.L and before api_token,
How to download a file having '&' in the URL with wget in Termux?

Put all the URL argument into a single quotes. You'll get something like this:
wget -O /storage/emulated/0/Download/worldtradingdata-realtimeprices.csv 'https://api.worldtradingdata.com/api/v1/stock?symbol=AHT.L,AZN.L,AUTO.L,AVV.L,AV.L&api_token=39W3kqXKo1zm04k5De0yutk7iNtEKygnYPqDTowXy94EwgBUNAb3yY3XHHbN&output=csv/worldtradingdata-realtimeprices.csv'

Single quotes will disable special meaning of meta-characters like &
In addition, I'd suggest you to regenerate the api token.


text:
Frequent audio dropouts on bluetooth, is it possibe to increase BT emission levels
I have a Xiaomi Note 7 and AKG Y500 headphones. I experience very frequent audio drop-outs unless I keep the phone close to the headphones (in my shirt pocket...).  The same headphones work flawlessy with my PC. Experimentally, checking at home how far I can go before getting drop-outs I have a lot more range with the PC (at least 8 metres) than with the phone (3 meters tops), so I conclude that the emission level of the headphones could be insufficient (the other hypothesis is that the phone isn't sensitive enough to get the return signals from the headphones).
Is there any way to increase the BT emission level of the phone?
Running Android Pie.

Is the Bluetooth connector of the PC an small USB connector or an integrated one (e.g. in a notebook)? If it is the latter the difference is the antenna which is larger as the notebooks as more free space as a small smartphone.

@Robert Yes, it's an integrated one. But if the phone antenna is less efficient they can send more power to it....

I think the more sever problem is that Wifi uses the same frequencies and in the smartphone the antennas are more close to each other resulting in more disturbances. On a notebook they are usually far away from each other to minimize this type of problems. Disable Wifi on your phone or try this guide and check if that helps.

The problem is more acute when I am in the streets, normally farther from Wifi than at home. Will try next time I go out (in several weeks:))

So you are comparing the Bluetooth quality from your PC at home with the Bluetooth quality of your phone while walking somewhere around? Such a comparison does not necessarily mean that the smartphone has a bad Bluetooth quality. It may simple mean that the 2.4GHz band (which is used by dozens of protocols like Wifi, Bluetooth, ZigBee, wireless video transmission systems, ...) is so occupied out on the street that interruptions are inevitable.

I'm not the only one with BT headphones in the streets... And at home, that bathes in Wifi signals, the BT signal from the phone is much more disrupted than the one from the PC (tried the suggestion to disable wifi on the phone, BTW).

Then it may be that Bluetooth on the PC is a class 1 or 2 device (100/50m range) where as the Smartphone has only a class 3 Bluetooth device (max 10 meters). AFAIK the Bluetooth signal class can't be changed, it is a hardware property.


text:
How to share a 4G data connection over wired Ethernet?
I understand that Android is principally an wired-Ethernet client.  i.e. it requests and receives a DHCP address.  The internet is on the other side of the Ethernet cable.
Does any version of Android have the capability of running its wired-Ethernet in an "access-point", "tethering" or "server" mode, where Android's Ethernet provides a DHCP server and NATs Ethernet traffic out through its 4G radio, to the internet?

While the feature has never been part of stock Android (not sure if some custom ROM provides this), it's possible on rooted devices.
I recently answered to How to make Ethernet work on Android over OTG? which may help you make Ethernet work on your device. Once done, there are two more things required:

Run a DHCP server (we already have dnsmasq on device up to Android 9, or you may get a static binary)
Share internet (by doing IP forwarding and NATing)

Both of these steps are explained in my answer to How to create a WiFi hotspot from the terminal? and the answers linked there. Just ignore the steps related to WiFi and pick the relevant parts.


text:
Can't use/format SD card formatted as internal storage
I have a SanDisk Ultra 16 GB SD Card and formatted it as internal storage in my Nokia 2.1 (Android 9 - Not rooted).
I can't use or format the sd card on my phone.

When I choose to format it as internal storage, I get the following toast:
Attempt to invoke virtual method 'java.lang.String android.os.storage.VolumeInfo.getId()' on a null object reference.
When I choose the other option - formatting as removable media - the format process finished but nothing happens and my SD card is still unknown to my phone.

So I decided to format it with my computer. This is what gparted shows:

When I delete these two partitions, the operation completes, but I still have those partitons!

When I try to delete those partitions and create a new FAT32 partition using GParted, I get the following error:

create empty partition  00:00:04    ( SUCCESS )

path: /dev/sdb3 (partition)
start: 2048
end: 31115263
size: 31113216 (14.84 GiB)
libparted messages    ( INFO )

Can't have overlapping partitions.
Partition(s) 3 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

So I tried writing zero to the entire disc, using dd:
[dsm@dsm-pc ~]$ sudo dd if=/dev/zero of=/dev/sdb status=progress
[sudo] password for dsm:
15928488448 bytes (16 GB, 15 GiB) copied, 3894 s, 4.1 MB/s
dd: writing to '/dev/sdb': No space left on device
31116289+0 records in
31116288+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 3922.32 s, 4.1 MB/s

Nothing happened after that, I still have those partitions!
I don't need my data, is there a way to format this SD Card? I checked many similar questions here and in other websites, but none of them helped.

it's a unkown problem nobody has solved yet https://android.stackexchange.com/q/221269


text:
Can't enable Developer Mode on Nexus 7 2013 with tapping the Build Number
I am trying to root Nexus 7 2013 and for the purpuse I need to enable USB debugging. As instructed from multiple resources, to enable developer mode one needs to tap the build number 7 times. Did that, plenty of times, but nothing happens.
I saw this other question on the matter, where the case appeared to be that there were multiple users, but in my case there is just one user on the tablet.
About info picture: http://prntscr.com/rmo70x

Please give this solution a try

I don't know if you missed steps following the official process

Just fyi this link is 404

The problem was that the tablet had installed Family Link. Once I removed the account from Family Link, tapping the build option worked.


text:
Android: Change file-contents under /system/etc with Magisk
I would like to change a configuration file under /system/etc or /etc. Neither of those locations are writeable and I can't make them writeable with a rw remount. The device is "rooted" with Magisk.
How can this be done?

magisk is systemless root method. modifying system will break with all benefits magisk provides, and most likely trigger dm-verity protection. you should use bind mount overlays instead. however, on system-as-root devices you must remount rw / instead of /system


text:
Bluetooth Speaker Controls Too Loud and in Too Few Steps
I bought a set of Dali Zensor 1 AX speakers which has a Bluetooth connection. Playing over the 3.5mm cable works perfectly and the volume can be nicely adjusted from the phone. The phone has 31 volume steps, with 0 being muted and 30 being 100% volume.
However, when I connect the same phone via Bluetooth, there are only 4 steps of volume control:

0 on phone: muted
1 on phone: 33% speaker volume
2 on phone: 66% speaker volume
3 on phone: 100% speaker volume

Steps 4 to 30 are all there but because the volume is already at 100% on step 3, they do nothing.
Having only 3 controls is extremely unpleasant as it's unlikely the volume I want to listen to is one of those 3 and to make matters worse, most often when I connect to the speakers it's higher than step 3 and just blasts whatever I play at 100% for a few seconds while I try to turn it down.
I've tried connecting an iPhone to it via Bluetooth and it works perfectly fine. I've also connected multiple Android phones (OnePlus 5T and OnePlus 6T) and they both show the problem.
How can I get my Android phone to spread the Bluetooth audio volume control across all the steps rather than just the lowest 4?

After a couple of hours of searching I found the fix:

Enable Developer options if you haven't yet (instructions can be found online).
Open Developer options.
Enable the Disable absolute volume option.
Enjoy listening to music at whatever volume you like.

Here are the details for this option:


text:
"Ready to connect when quality improves"
My Galaxy S10e shows near my home WiFi's name:
Ready to connect when quality improves

Even though the WiFi works very well (using it right now from laptop).
The phone has no cover, and no obstacle to the router which sits two meters away.
What could be the problem?

In my case, I had a manual proxy configured for this WiFi, and the proxy was not working correctly.
Removing the manual proxy configuration solved the problem.
To check if you have one, tap the WiFi, then tap "Advanced", then make sure "Proxy" is set to "None".


text:
Will a CDMA carrier's LTE work on a GSM-only phone?
More specifically, I'd like to know if a Sprint-based carrier (Tello) will work on a Xiaomi Redmi Note 8 (M1908C3JG).

No
Will my phone work says Redmi Note 7 does not work on Tello.
Readme Note 7 has more operating frequencies than Readme Note 8 (see Network section-
Note 8 frequencies are a sub set of Note 7 ) but Readme Note 7 doesn't work with Tello.
If you switch carriers, you have a 25 % coverage as indicated here, but that would need you to do homework to find out which carrier and if that frequency (s) are used where you operate


text:
How to inspect HTTPS traffic of a third-party app on Android 9+
I want to inspect inside HTTPS-encrypted packets that an app is sending. It is not my app, I don't have its source code.
My device is rooted, so I can modify /system/etc/security/cacert if needed, for instance to do man-in-the-middle proxying.
Up to Android 8, one could just install a self-made certificate, but it does not work anymore. I have Android 9, but I can upgrade if needed.

I've heard good reviews about this app in some forums. No personal experience /affiliation

As tipped by @beeshyams, HttpCanary is perfect for this.
You need a rooted device, of course.
HttpCanary takes care of all of the difficult steps (certificate generation and installation) transparently.
It shows a list of requests (filterable by app), and details of each request and response.
The best feature is this overlay showing request while I am using other apps (bottom right):

Even though the Google Play page says "HttpCanary core codes are opened in Github", https://github.com/MegatronKing/HttpCanary does not contain most of the source code, so I believe it is not open source.


text:
Device serial number (using ADB commands)
I'm using an automation platform that has an ADB session which requires the device_serial_list, which is the serial number.
However, if I do adb get-serialno I get a different value than the one shown in this website
Edit: when you input your IMEI, it shows you several info about your phone and one of them is the Serial Number which is different than the previous one, so I'm not sure what should be the one to use in this case.
Edit 2:

The previous pic comes in a link starting by "https://www.imei.info/check/lg-warranty-checker"

adb devices will display device serialno

@alecxs You are right but this command will result in xxxx device as the output and since OP is automating, device will need to be stripped whereas get-serialno only returns the number.

It looks like you are confusing two different numbers:

adb get-serialno gives you the serial number of the device.
Link in your question is referring to  IMEI number which can be obtained by adb shell service call iphonesubinfo 1
(see  this and this for more)

Going by the context, you should use the first number (serial number) and not IMEI number.
Both serial and IMEI numbers are usually found in the about phone section in device settings.
Edit: Post the edit made by OP, I entered my device IMEI number and it returned the following info, only format shared here, not actual digits
 IMEI.info: TAC: AAAAAA FAC: BB SNR: CCCCCC CD: D [1]
The serial number you are referring to SNR above is the 6 digit (6 C's) is the serial number, which is manufacturer-defined,
NOT the serial number returned by adb (verified, adb command returns 8 digit serial number)
So, the answer remains same, use the adb command output

Additional Info
[1]: Output in the linked site corresponds to pre 2004
format

As of 2004, the format of the IMEI is AA-BBBBBB-CCCCCC-D, although it may not always be displayed this way

(see section - Structure of the IMEI and IMEISV (IMEI software version) in the IMEI wiki

No, but in the website, if you input the IMEI it shows you a Serial Number. I know they are 2 different things :)

@Natiya in that case, it is best if you post a screenshot. I tried that website and I couldn't get a serial number for the IMEI I used (from google images, a Galaxy S4).

Natiya 1. Please make it a point to be as clear as possible in the question, so that the answer can be relevant and not end up wasting time of the person who  answers. I was tempted to down vote your question on this account but I didn't 2. If you had bothered to read the linked  IMEI wiki, it would have been clear (there's a reason for citing sources) 3. I trust the revised answer makes it clear. If not, ask. @Firelord as FYI since you too have a OnePlus

I'm afraid the SNR you mentioned in the answer is not the same I'm referring too.  I'll try to add a screenshot

@Natiya Linked page points to LG devices. There is no page that corresponds to my device  that gives this extra information, so I can't check. The SNR number in the screenshot, how is it different from 1. adb result 2.SNR as in my answer. I am asking in terms of number of digits, alpha numeric etc but even if you give you this information, I doubt I can answer for sure because I can't check

ESN is likely referring to Electronic Serial Number which is for CDMA phones and comparable to IMEI number for GSM phones. You can read the linked site. I can't verify for my device from that site. Sorry, I can't help beyond this point


text:
Can I install TWRP with stock recovery via apply update from sd card if I change the file to update. Zip? I'm on zte trek 2
Can I install TWRP using stock recovery and sd card?

not on stock recovery, but with SP Flash Tool if yours has Mediatek chipset

Do I have to be rooted and how do I find out what my chip set is? Thanks for answering

Found out I think it's qualllcom snapdragon

rooting is recommended because this way the necessary modification (disabling dm-verity) are done already, but root is not required for SP Flash Tool

Cool thanks any way to root without PC or kingroot? I tried that and kingroot. Don't work.

If I was rooted I could install TWRP no PC no problem. I don't have access to a computer only wifi

forget kingroot or other rooting apps, rooting is only possible with unlocked bootloader (forces factory reset) which is only possible with PC. with this app you can figure out chipset http://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw

Ok thanks allot !

Root is definitely needed for so flash tool

rooting is a colloquially description for the availbility to execute apps or commands with root privileges (usually a superuser app is installed which manages app permissions based on your choice). flashing partitions (for example twrp custom recovery) does definitely 1) neither require rooting 2) nor won't root your device. for rooting you must install Magisk or SuperSU which can be done via TWRP or by flashing magisk patched boot.img from fastboot (or flash tool)

I know this. I need to know how to install TWRP without PC or root. Is it even possible?

if your device is Mediatek you can root with bootless root method on locked bootloader without PC https://forum.xda-developers.com/showthread.php?t=3922213&page=101

(Mediatek) SP Flash Tool / (Qualcomm) QPST is software for PC only

if you have another rooted device with usb otg support you can install fastboot for arm and connect two devices with usb otg cable. with this you can unlock bootloader and flash from fastboot without PC

Thanks for help and sorry to say this is my only device


text:
Recovery mode doesn't work
I've followed these steps to try to root my phone. Then, I continue following this guide but I'm stuck where it says "Paso 2":
I'm trying to access the recovery mode in my PC with the adb reboot recovery command but my smartphone shows the "No command" message and icon on the screen and after I while, it just restart normally.
I just wanted to install Magisk so I did.
C:\adb>adb reboot-bootloader

C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (21104 KB)...
OKAY [ 0.491s]
writing 'recovery'...
OKAY [ 0.235s]
finished. total time: 0.736s
C:\adb>fastboot reboot
rebooting...

finished. total time: 0.010s

and then I was expecting to be able to enter the recovery mode, but I've tried all the possible key combinations and I can
Actually, before the "No command" screen I get a warning message asking me to visit: g.co/ABH saying that "your device software cannot be checked for corruption. Lock the bootloader. PRESS THE KEY POWER TO PAUSE BOOT. Your device will boot up automatically after a while" and it just restarts normally
I also found this file: /system/recovery-from-boot.p I've read this is preventing me from entering in the recovery mode, but as I'm not root, I can't find a way to delete it or rename it...any suggestion, please?
More info about my phone:

Also, my goal is to install Magisk, so if there is any other way to do it, it will be welcome too.

Comments are not for extended discussion; this conversation has been moved to chat.

Duplicate of: What does the "no command" screen mean? (Trying to execute hard reset Recovery)

When you are in fastboot mode you can directly start the recovery image without installing it:
fastboot boot recovery.img

Alternatively if you want to start the installed recovery rom execute
fastboot flash recovery recovery.img
fastboot reboot bootloader

and then select Recovery using Vol-Up/Down buttons + Power button to start the recovery ROM.
Note that some stock firmware images will replace the recovery ROM back to the original one once you start the main OS. This is automatic "updating of the recovery ROM" is part of the boot process.

Comments are not for extended discussion; this conversation has been moved to chat.


text:
Share clipboard data between users on multi-user (secondary space) Android?
Leaving security concerns aside, is there a reliable way to communicate data via clipboard between users on a single device without using network methods? For example just to copy a link in the primary space  and  then access it later via clipboard in the secondary space. App suggestions are welcome.
NB: There is already an option to import/export files,photos etc (but not clipboard sharing)
Running MIUI 9, Android 7

How about Chrome Tab Sync or TabCloud?

This secondary space implementation seems to differ in OnePlus devices. In my Android 10 on OnePlus 6, I can share clipboard between primary user apps, work profile apps, and parallel space apps. However, as expected, clipboards are not shared if user profiles are switched into using settings app.

IIRC SMS can be explored - by sending a SMS to yourself and accessing in other user. I haven't checked

Is MIUI's secondary space an implementation of multi-users or managed profiles (https://source.android.com/devices/tech/admin/multi-user)? // The app you are using to copy data copies text, URI or intent (https://developer.android.com/guide/topics/text/copy-paste#Clipboard)? // Are you able to paste in primary space using the same app you are using in secondary space?

@IrfanLatif In MIUI there is a slightly different implementation of the feature, it is designed for users "to have their own apps, files, folders, photos, and so on", in this case app data and files aren’t shared between users, and one has to import/export the required files in order to access them. I can't paste directly between spaces

@beeshyams that is clever idea, it works even if private messaging is off, I can create a draft a message and can I access the "text" +1

@alecxs thanks hadn't tried that

@Firelord MIUI implementation seems different though since each user as a completely seperate space, and can't even share app data (although you can do it with apps)  max users is 2

@xavier_fakerat good. If it works you can post that as an answer!


text:
Is it a bad idea to let your phone keep charging all the time?
I read somewhere that long periods of charging can be bad for the battery and the best level to keep your battery at is around 50%. Is this true?
If it is then after how long will the battery show any signs of being affected?

There are two simple signs that your battery is affected: 1. the charge capacity is reduced 2. the battery is blowing up which usually leads to your phone getting a bulge or if this continues I have seem smartphones that "disassemble" them-self because the battery got larger and larger (that were older iPhone 6 connected 24/7 via USB to a computer).

For the first part of your question, see Ideal charging / discharging percentage for maximum battery life?. Answers there explain in detail, so yes, it is true
Second part, after how long... depends on how often you charge it the wrong way, your usage (how many cycles of charge) etc and one cannot put a figure to it. Bear in mind that batteries even without being used lose a significant amount of life due to aging. So, it's a bit complicated to separate cause and effect. I don't think it will show up soon but maybe about an year or so (no backing to substantiate)
See answer here for more details Battery capacity wear-down, and its relationship to charging practices


text:
Nokia 7.1 won't boot after Google Security Patch update
My phone (Nokia 7.1, Android 10) downloaded a Google Security Patch update over night and asked me to reboot the system for installing the patch. But after the reboot, it said that the system is corrupted and the phone needs a factory reset. I don't want to lose the data on the phone.
I can get the phone into Download mode and communicate to it via fastboot and I tried to use adb to sideload the original Android 10 image (29ad19....zip, which is build 4_08D), but it won't let me install it because the build timestamp is older than my current system's build timestamp and it refuses to let me downgrade.
I tried re-installing the latest security patch (4_08F) from here via adb but the system says that this patch was meant for 4_08E not 4_08F. This is confusing because if the system had trouble installing this patch in the morning, it should have stuck with 4_08E, right?
My questions to the community are as follows:
1) Can I force my phone to downgrade and install an older system without losing my data? If so, could someone point me to the correct instructions?
2) Are there newer updates for Nokia 7.1 that I've not found which I should be trying to install?
Thanks!

Question 1. Sorry, no because of rollback protection that was introduced with Android 8. Question 2 it's best to check in device forums, XDA, reddit and such sites which are dedicated to discussion on your device.

It is a fairly common sight on a "Nokia 7.1". Did you try this tutorial already? The slots can essentially take you 1 version behind and you can then try booting. Sometimes that works (as in the comments sent by many). And since you want to preserve your data, there's even lesser chance that it will work, but it can.
If not, what you can try is to go one version behind (by changing the boot slot -- fastboot --set-active=a or b as needed) and then try to sideload the latest update via recovery again. As with updates, they can only take you forward and not backwards. The 408F is the newest update for the phone and you cannot find an update newer than that. When you'll change the slot, you'll be on 408E and then the 408F should install just fine.
As about your question about how the update got installed, it's the beauty of A/B devices, but the issue isn't with installing the update, it was done successfully. The issue is more of the device not managing to get its encryption running after the update has finished installing. The system feels that the update was successfully installed, but the phone clearly knows that something went wrong with the data encryption/decryption process.
In case changing the boot slot and then installing the update doesn't help, then you're left off requiring full firmware installation. You can send to Nokia or buy a remote flashing service. If you still haven't done a reset until this point, then the service can try to help bring your phone to a bootable state where you can backup your data.

Just had this happen to one of the two nokia 7.1 phones that we have. Not a good experience as both of them have been sent back for hardware issues in January now this. Nokia support blames Google for the crashes with this update.  I know it is android one but i still thought the vendor controlled the updates and has to test it for each of their phones.


text:
Can I use an old SIM from a locked phone in my Redmi?
I've never had a Smartphone that I used as an actual phone with a SIM before. I have a Redmi 6 I bought overseas (Android 9, MIUI 11) that's only been used with Wi-Fi. I just cut short a long overseas trip due to the COVID crisis. I can't go out to buy a SIM. I can't get one delivered.
I need a phone number to do government stuff online. The online stuff won't work with my sister's phone as a phone number can only be used for one account. My nephew has an old phone with SIM that fits in my phone. The SIM is or was registered to him but has not been used for six to twelve months. The phone was surely locked as is usual for cheap phone packages in Australia. I have no clue whether SIMs are locked to certain phones, or just phones are locked to certain SIMs or certain carriers.
Putting his SIM in my phone, it recognizes the SIM, but not the carrier, phone number, or anything else. I couldn't send a text or receive a text. It does say I can make emergency calls only.
Is it even possible to use a secondhand SIM in my phone? Are my problems due to this not being possible, due to phone settings, or to do with the SIM or the phone service provider (Telstra)?
I can't find anything on the phone about setting up a new SIM. Perhaps some SIMs can only be registered once and are locked to the phone they were packaged with?
Because I'm so totally clueless and my situation has more than a few unique characterists I haven't had any luck Googling a solution yet.

It really depends on your carrier. Six years ago, I was able to move an AT&T SIM card that had been locked to an iPhone 5 to an unlocked Nexus 4 without issues (in the U.S.). What you might run into, though, is incompatible frequency bands. I'd contact your carrier.

Yep, reading further into your question, the issue appears to be your new phone not supporting the same frequency bands.

@gparyani: I could well be wrong but I thought in Australia we only used one band and I checked in Taiwan when I bought the new phone to be sure it would work in Australia too. But I will definitely look into it properly. Thanks for the lead!

AFAIK, SIM is tied with the carrier and not device (doesn't make sense to tie with device, what if device goes faulty?) so the possibilities are 1. Your phone and SIM are incompatible wrt frequency bands as already suggested 2. SIM is possibly blocked being inactive for a while 3 SIM is faulty

@beeshyams I checked the freq. bands for both my phone and the sim's phone and they seem compatible. in some parts of my phone it recognizes the carrier, but other places not. maybe some are just user-filled text fields? i think most likely is inactive for not being used for a while. Trying to verify that...

You can also call the carrier or see on line how to manually enter carrier specific APN settings. Without the correct APN settings, you will not be able to use the phone. Usually, on inserting SIM the carrier sends APN settings to your phone via SMS and you need to simply click to approve - this is with reference to your phone showing carrier info in places

The APN settings do show up correctly on the phone as compared to what I find via Google.

ATM that leaves us with faulty or deactivated SIM as possibilities @hippietrail

@hippietrail Just a dump question: If the SIM has been "not been used for six to twelve months" most likely the contract has ended and hence the SIM card has been deactivated by the carrier. Even prepaid usually get disabled after 6-12 month without loading money onto it. Hence the sim card may be fully functionally (from a physically point of view) but the carrier has just disabled it.


text:
Is there any command to launch directory of file manager in android phone using adb?
I want to open Download folder in my android phone using adb. I have example command for different terminal:start . /path/to/that/folder command for command-prompt and nautilus /path/to/that/folder for ubuntu terminal. Please help me to find the adb shell command..

See https://android.stackexchange.com/questions/45070/starting-an-activity-listed-under-settings-from-terminal-or-adb-shell . It is a good start.

It depends on what intents the apps installed on your device can handle. am start -a android.intent.action.OPEN_DOCUMENT -d /sdcard/Download -t '*/*' works with many file explorer apps.

@IrfanLatif , These command only open recent activity file. Please help to find the command for Redmi phones..


text:
Galaxy Note3 is not recognized by Odin ("SeAndroid not enforcing: set Kernel")
My Galaxy Note3 is not recognized by Odin because its stuck in recovery with SeAndroid not enforcing: set Kernel. When I reboot into TWRP recovery, it's recognized by the computer but still fails to acknowledge on Odin.

Device: SM-N9005T Samsung Galaxy Note3.
Odin Downloader: 3.10 (I also have version 3.07)
Computer: desktop running Windows 7 Ultimate

https://duckduckgo.com/?q=%22SeAndroid+not+enforcing%22

you probably flashed wrong twrp, now your device stuck on splash screen. the SeAndroid headline seems unrelated to your problem and is misleading. kindly edit your question. if you ask how to unbrick it would be helpful to list all actions you have done

i think you are mixing up things
Odin requires your device to be booted in download mode, not recovery mode. if you are in twrp you must leave revovery mode, you can reboot into bootloader from twrp menu. other method to boot into download mode is button combination Volume Down + Home + Power. then select Continue with Volume Up
SeAndroid not enforcing is just a info message which tells you everything is all right. for full access to partitions TWRP requires kernel which allow setting selinux permissive. if SeAndroid is enforcing it would prevent TWRP from working properly
side note: whatever you want to flash from Odin, you could do from twrp command line, too. twrp has full access to all partitions and skilled user can raw write partition images with adb push or dd

this answer is assuming you pass the SeAndroid not enforcing screen and twrp boots normal


text:
adb KEYCODE ENTER or 66 is not working in huwaei/Vivo phone to toggle the Airplane Mode
Using ADB Keyevent i am trying to enable and disable the Airplane Mode toggle option from UI, but its not happening...can anyone help me on this.
I tried with adb KEYCODE ENTER and 66 as well, but nothing works in my devices.

https://stackoverflow.com/q/10506591

This doesnt work , "Permission Denial: not allowed to send broadcast android.intent.action.AIRPLANE_MODE" .....even i tried using the ADB keyevents 66 but VIvo and huwaei phone has the Toggle option different compared to other phones and this Keyevent is not working....Kindly suggest some alternative

i am pretty sure you haven't tried all answers on the link above

@alecxs, thanks for replying back...before posting this question i have gone throw all the possible ways mentioned in the shared link and other website too..my phone dosen't hve root permission and the mentioned key events are also not working with this UI..plz suggest another option just to toggle the enable/disable setting from UI

make your own test with keyevent in any other app, for example spell a word by using keyevents

@alecxs, all other key events work, but when i try to enable/disable using the toggle option in UI with keyevents like  21 -->  "KEYCODE_DPAD_LEFT"
22 -->  "KEYCODE_DPAD_RIGHT"
23 -->  "KEYCODE_DPAD_CENTER" 66 -->  "KEYCODE_ENTER" ..... to select the toggle option and enable any features like Airplane Mode or mobile data ..so those toggling feature is not working....

what about KEYCODE_TAB, KEYCODE_DPAD_DOWN or KEYCODE_SPACE

ya i hve tried all the possible combination for this...but none of them worked.i just need to enable the toggle to Switch ON and OFF Flight Mode from UI for huawei Phones

then try input touchscreen tap x y with pixel coordinates of screenshot

alecxs @ for time being this resolved my issue...thanks for sharing info


text:
Other person's audio cuts out when I speak
When I'm using WhatsApp or Duo or any other VoIP calling app I've found so far, the phone (OnePlus 5T) seems to apply some automatic "echo cancellation" where it cuts out the other person's call if they're on speaker, every time I speak so I can't hear myself.
This persists even for a second or two after I stop speaking, and can make me miss some of what the other party is trying to say as they are effectively "muted".
I've tried turning off noise cancellation in the caller app without any change, and I can't find an option in WhatsApp or Duo. I've also only been able to test with the other person on an iPhone, so it may be on their end but if so is there a solution to disable it from their side?
I don't mind being able to hear myself - I use earphones. Is there a way to disable this "echo-cancellation" feature? I am rooted if necessary.

Wild guess, you can try this sound amplifier to see if it helps

@beeshyams I'm afraid not - I think it may just be an issue with the apps themselves...


text:
how to connect and disconnect from WiFi using ADB (not a root user)?
I found this project which allows me to connect to a WiFi through ADB commands not being a root user. I was wondering if anyone knows how to disconnect also from ADB and not being a root user.
UPDATE:
I've been recently trying:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date.  killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front

and
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front

I also found doing this type of command:
adb shell input keyevent 20 & adb shell input keyevent 23

I can navigate and click. The problem seems to be that I always finish in a different state so the next time I input the command
adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings

I start in a different place and start clicking elsewhere. I've tried returning home, but that doesn't fix the issue. Is there any way to start always from the same point inside the WiFi settings?
Thanks!

Comments are not for extended discussion; this conversation has been moved to chat.

You can use  adb shell cmd -w wifi connect-network  command followed by these parameters if needed :

-  connect-network  open|owe|wpa2|wpa3 [] [-m] [-d] [-b ] [-r auto|none|persistent|non_persistent]
    Connect to a network with provided params and add to saved networks list
    open|owe|wpa2|wpa3 - Security type of the network.
     - SSID of the network
        - Use 'open' or 'owe' for networks with no passphrase
           - 'open' - Open networks (Most prevalent)
           - 'owe' - Enhanced open networks
        - Use 'wpa2' or 'wpa3' for networks with passphrase
           - 'wpa2' - WPA-2 PSK networks (Most prevalent)
    -m - Mark the network metered.
           - 'wpa3' - WPA-3 PSK networks
    -d - Mark the network autojoin disabled.
    -h - Mark the network hidden.
    -p - Mark the network private (not shared).
    -b  - Set specific BSSID.
    -r auto|none|persistent|non_persistent - MAC randomization scheme for the network

For example. If you want your device to connect to wifi with ssid home with wpa2 authentication and password as 12345678, you should enter

adb shell cmd -w wifi connect-network home wpa2 12345678


text:
is it possible to delete a file from system folder without being root?
I found this file: /system/recovery-from-boot.p and I've read this is preventing me from entering in the recovery mode, but as I'm not root, I can't find a way to delete it or rename it...any suggestion, please?

https://android.stackexchange.com/questions/222361/recovery-mode-doesnt-work/222363?noredirect=1#comment288499_222361

Yes, it is possible to delete files without root. for example one could convert and mount system.img, delete files, re-convert into sparse image and flash modified system image (from fastboot or flash tool). But this special file you mention is renamed automatically from twrp (if you swipe to modify system on twrp initial splash screen)

@alecxs I flashed with twrp and it didn't change. I think the problem may be that twrp is not working on my phone


text:
Can't access my phone memory suddenly after using SD card as internal memory
A few weeks ago I integrated my SD card to use as phone memory. Everything was fine until a couple of days ago.
All of a sudden I saw the "insert SD card" notice appear on the notification bar. I open the back cover but the SD card looked like it was in place. I remove it and insert it back and the notice disappears. But then I notice that when I go to file explorer (FX) to access my files, it says "Access was denied". I can't access anything that is on my phone memory, although the apps are working. I guess system files are OK, but everything else is not.
My phone is rooted so I tried to access the files through TWRP but I can only see system folders.
Phone is a Moto C plus. Nougat.

Does this answer your question? How to decrypt the corrupt SD card formatted as internal storage?

You can recover some files from corrupted MicroSD Card. adoptable-storage is encrypted, it requires the encryption key from the source device. In your case you are lucky your device is rooted

insert MicroSD Card into PC Card Reader. figure out which one is the correct block device (/dev/sdc) with sudo blkid

mount your hard drive (/media/xubuntu/404CCE454CCE3606). check free disk space with df -h

clone 1:1 disk image of the entire MicroSD Card with gddrescue
sudo -i
apt install gddrescue
cd /media/xubuntu/404CCE454CCE3606
ddrescue -n -b512 -r3 /dev/sdc sd.img gddrescue_sd_img.log

install android platform-tools
apt install android-tools-adb android-tools-fastboot

connect your device in recovery mode (TWRP)

get the encryption key file expand_5f5e697154132edfaa6fca7ac23cde2a.key (root access required)
adb devices
adb pull /data/misc/vold

read the 16-bytes hex encryption key (ae126af293501cd130db0637372e8911)
ls vold
hexdump -v vold/expand_5f5e697154132edfaa6fca7ac23cde2a.key

map the image file to create loop devices
kpartx -av /media/xubuntu/404CCE454CCE3606/sd.img

get partition size (62299103) and decrypt the 2nd partition (/dev/mapper/loop1p2)
blockdev --getsize /dev/mapper/loop1p2
dmsetup create crypt1 --table "0 62299103 crypt aes-cbc-essiv:sha256 ae126af293501cd130db0637372e8911 0 /dev/mapper/loop1p2 0"

when successfull a new (decrypted) block device /dev/mapper/crypt1 (ext4) will created

mount the partition (skip this step Xubuntu will auto mount)
mkdir /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448
mount -t ext4 -o ro,noexec,noload /dev/mapper/crypt1 /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448

Open new terminal (CTRL + ALT + T) and start File Manager (root session) from command line:
sudo thunar /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448

in File Manager enable - View - Show Hidden Files
you should see some directories
app
local
lost+found
media
misc
user
user_de

you can now browse media directory for Internal Storage and copy your Pictures to your hard drive

Be aware you can't copy app directory to windows hard drive, because linux permissions and file names aren't compatible with NTFS file system type

however, you can create tarball archive to preserve the whole partition content including all metadata
 sudo -i
 cd /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448
 tar --selinux --xattrs -H posix --numeric-owner -vcp * | gzip -cn > /media/xubuntu/404CCE454CCE3606/sdcard.tar.gz

sdcard.tar.gz can be unpacked with 7-zip in windows, or restored from twrp command line with GNU tar

on the last step, can you please double check disk usage of sd.img? are there files in it? (if you already have sd.img skip creating again and start with kpartx) when mounted run df -h /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448 or find -type f /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448

I can see in the phone system root folder in the phone. And it has only 203 MB as well. My concern is...if I "forget" the SD card, will I lose the files from the "phone" internal storage? Because right now I can't access the phone internal storage. I can only see the system folder. But I can see the folders in the adopted SD card (which are almost empty).

but what about the files in sd.img?

Size: 30G | Used: 239M | Avail: 29G

Could it be that it was saving most of the data (or all of it) in the internal phone memory instead of the SD card even though they are both integrated? But now my files are being held hostage in the phone memory. If I want to "unlink" or "unadopt", what are my choices? From what I can see, there are 3 ways...1) insert a new SD card and adopt it as internal storage WITHOUT "forgetting" the first SD. 2) "Forget" the adopted SD 3) "Migrate" the files from the internal storage option (even though it says "it will free 0 bytes on SD card"). And then "format" the SD card as portable". Which one?

if 1) is possible that seems the best option

you should run extundelete or testdisk or photorec or binwalk on /dev/mapper/crypt1 maybe there can be some files recovered (search for that keywords here or www)

"Sudo extundelete /dev/mapper/crypt1 --restore-all" ??

yes that will scan for deleted files based on inodes. you can also run these tools on your internal storage data.img

From TWRP?.....

to create such image (if don't have already) run that command while connected in TWRP:
'adb pull /dev/block/dm-0 data.img' or if not encrypted 'adb pull /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata data.img'

with this tools you can scan your internal storage and your adoptable storage for deleted files as well. photorec is more powerful, binwalk the deepest file search. testdisk has also some options to restore deleted files but that tool is more for repairing partition tables and maybe just as good as extundelete

here is example usage for testdisk (little complicated) the red files on that screenshot are deleted ones https://android.stackexchange.com/a/219364 see you tomorrow, it's late

I'm running extundelete and it's taking a long time. There is no indication so I have no idea if it's working or it hang.

Where is it created?

check home directory ~/RECOVERED_FILES


text:
Can't delete photos from my LG X Power
Updated with more information -- please see below
I have an unrooted LG X Power running Android 6.0.1.  I have recently gone through Google Photos (using a desktop web browser) and deleted a bunch of videos, but even though Photos tells me that they will be removed from my devices, they remain on my phone, and I can't seem to get rid of them.  When I try to delete them using the Photos app on the phone, I get the error message:

Can't delete [x] items
Photos doesn't have access to delete items on your SD card. Go to the Gallery app to continue deleting.

But I don't even have a Gallery app on my phone! Moreover, when I use a file browser to see what's on my SD card, there is no trace of them; they do not appear in the DCIM > Camera directory (although my photos do).
Where are these videos hiding?  I suspect they are hidden somewhere in my internal storage, as I am rapidly running out of storage space, but the DCIM > Camera directory in my internal storage is completely empty, and I can't seem to find any other large directory.  Why doesn't deleting them from Google Photos remove them from my phone?  And why does Photos keep telling me to use a nonexistent Gallery app to delete them?
Edited to add: As far as I can tell, Photos does have permission to access the SD card; it says so in Preferences, and is able to save photos and videos there with no problem. It only throws up an error message when I try to delete. Furthermore, the error seems to affect photos and videos taken recently; older photos and videos (which were all taken on a different phone) can be deleted with no difficulty.
Further updates: Well, I found them!  The files are not on my SD card, but rather are in my internal storage.  But the plot thickens:

Using the DiskUsage app by Ivan Volosyuk I was able to find the files hidden in my DCIM folder on my internal storage (which is odd, because Photos keeps telling me that it can't delete them because it doesn't have access privileges for my SD card...  which it does...  but anyway...).  The folder, according to this app, contains about 5.9 GB of media.  (There's also a Podcasts folder with 1.33 GB that I'd like to get rid of, also...)  See screenshot below, then keep reading for more of the mystery!

When I try to delete the files (whether one at a time, or the whole folder at once) I get an error message:  "Error: file wasn't deleted."  No additional information about why the file wasn't deleted is provided.  See screenshots 2 and 3 below, then keep reading for more info!

To further compound my frustrations, the files (and folders) in question don't show up when I use other file browsers.  Here, for example, is what I see in Android File Transfer (see my last screenshot below). Notice that the DCIM folder exists, but is essentially empty, except for a few thumbnails; the Podcasts folder isn't shown at all.  I get similar results when I use the stock File Manager app on my phone, and when I use this other File Manager app, and when I use Files By Google: none of these apps show the existence of the files in question at all.  And yet they're there, taking up space, visible in DiskUsage.

I'm hoping that with this additional information, someone can help me figure out how to finally delete these damn files.  I could really use that 7 GB of space back.

Using SD Maid - system cleaning tool (free version) to clean the device and delete those files using built-in file explorer solved the problem for OP. From app description

Nobody is perfect and neither is Android.
Apps you have already removed leave something behind.
Logs, crash reports and other files you don't really want are constantly being created.
Your storage is collecting files and directories you don't recognize.

That said, I have no clue of what exactly caused the problem and why other apps couldn't delete the files. Or how this app fixed the underlying issue.
I am not affiliated with the app. I've been happily using the pro version for years with scheduled operations to keep the device clean.

I suggest you try deleting the files with Total Commander.
Note (perhaps related):
It happened to me before that I have removed all files in a .thumbnails-XXXXXXX folder (about 900Mb), and they were actually gone (as opposed to your case, where you see your files persist).
But that space was never recovered. And I found others reporting the same issue.


text:
/data's data is garbled in TWRP. How to decrypt
So  this is quite another android story but I promise to keep is as short n dry as poss.
The issue was some of my Apps weren't able to access  /extsd folders with non root & so I deicided to give magisk module app systematizer a shot. With that also installed Pixel3fy  ( or whatever heck its called ) & & Viper4Android
 I dunno if that has any bearing. Removed Pixel after I booted on a blank screen and data got encrypted ( due to that Pixel Mod ? No sure. I can mount /data but all file names under L1 folders are encrypted aka garbled  ) . I am running  Q Havoc on top of TWRP  on Qualcomm chip mobile . Earlier , TWRP would ask me my pattern and decrypt /data and /system and I had access to these via TWRP. Now ( related to Mod installation ? ), it does NOT ask me for pattern and I can mount these partitions but they remain encrypted. I want my internal data . So Format /data is not an op.
What I did:
-- reinstalled this TWRP + Vmeta via Fastboot.( hoping that the pattern will come back again but went futile ) After that no OS load. Just reboots to TWRP
-- Followed this by installing boot.img + magisk zip again and Disable_Dm-Verity_ForceEncrypt zip

after all this it could BOOT TO LOGO and then HANGS ON LOGO
Questions :
-- How do I get TWRP to decrypt /data ( esp int. storage ) .After that I dont mind doing a fresh install after /data format . I want my int data.
--alternatively how can I successfully boot any way so I can backup my internal data
-- take a look at this, where he says you can  decrypt data by backup --> format --> restore. But /data is encrypted so backup and restore ...isn't it futile ? if I backup this data some form. My understanding is that its useless cos its encrypted and  restore will be fruitless since the data is encrypted with Unlock pin + key stored in Meta partition. I dont have any more backup. My last Nandroid was of stock rom. The /recovery /vendor  are same /system and /data are not. I in fact tried /recovery Nandroid restore - no use

After that I  can do a 'format' and get my OS working.

A subtle clarification. Once I removed the Pix3ly module I could boot the phone. TWRP  would not decrypt data after I tried command line
adb decrypt twrp <pattern>

I  thoughtlessly shot myself in the foot by not backing up  my partitions via TWRP and ended up doing a TWRP reinstall, which is when I got stuck-> will only boot to recovery --> ( flashboot boot.img + Magisk ) --> Now it will not reboot to recovery but stuck at Logo. Thats where I am now.
So yes any potentially offending module was removed  and that got me to boot but TWRP re-installation hosed everything. Desperate not to loose data I installed orange fox recovery to see if that can decrypt ( of course never had hi Hopes ) and still no light .  stock recovery cant handle Havoc. Stock ROM is Pie and this is Q so that wont match and even then issue is /data is not getting decrypted so any ROM wont boot is my humble , nimble  understanding but do let me know if there's something that can work
    Starting TWRP 3.3.1-milankragujevic_9.0_v1-8c0bcc8b on Sun May 31 06:29:22 1970
 (pid 406)
I:=> product model: 'Redmi (A'
I:=> using device id: 'Redmi_A'
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/class/android_usb/android0/f_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 2047 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (720 x 1520)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.791667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/recovery.fstab
I:Reading /etc/recovery.fstab
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/system_root'
I:Created '/system_root' folder.
I:Processing '/system_image'
I:Processing '/vendor'
I:Processing '/vendor_image'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/cust'
I:Created '/cust' folder.
I:Processing '/misc'
I:Processing '/external_sd'
I:Created '/external_sd' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:File Based Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using Keymaster HAL: 4 from QTI for encryption.  Security level: TRUSTED_ENVIRONMENT, HAL: android.hardware.keymaster@4.0::IKeymasterDevice/default
begin failed, code -62
Upgrading key in memory only: /data/unencrypted/key
upgrade_key failed, code -38
e4crypt_initialize_global_de returned fail
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Settings storage is '/data/media/0'
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:No /data/system/storage.xml for adopted storage
Updating partition details...
I:App found at '/system_root/system/priv-app/twrpapp'
I:Data backup size is 9887MB, free: 9730MB.
...done
I:Unmounting main partitions...

Partition Logs:
/boot | /dev/block/mmcblk0p52 | Size: 64MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p52
   Display_Name: Boot
   Storage_Name: boot
   Backup_Path: /boot
   Backup_Name: boot
   Backup_Display_Name: Boot
   Storage_Path: /boot
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/recovery | /dev/block/mmcblk0p53 | Size: 64MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p53
   Display_Name: Recovery
   Storage_Name: recovery
   Backup_Path: /recovery
   Backup_Name: recovery
   Backup_Display_Name: Recovery
   Storage_Path: /recovery
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/system_root | /dev/block/mmcblk0p59 | Size: 4092MB Used: 1453MB Free: 2638MB Backup Size: 1453MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p59
   Display_Name: System
   Storage_Name: System
   Backup_Path: /system_root
   Backup_Name: system_root
   Backup_Display_Name: System
   Storage_Path: /system_root
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/system_image | /dev/block/mmcblk0p59 | Size: 4096MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p59
   Display_Name: System Image
   Storage_Name: System Image
   Backup_Path: /system_image
   Backup_Name: system_image
   Backup_Display_Name: System Image
   Storage_Path: /system_image
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/vendor | /dev/block/mmcblk0p60 | Size: 975MB Used: 672MB Free: 303MB Backup Size: 672MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p60
   Display_Name: Vendor
   Storage_Name: Vendor
   Backup_Path: /vendor
   Backup_Name: vendor
   Backup_Display_Name: Vendor
   Storage_Path: /vendor
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/vendor_image | /dev/block/mmcblk0p60 | Size: 1024MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p60
   Display_Name: Vendor Image
   Storage_Name: Vendor Image
   Backup_Path: /vendor_image
   Backup_Name: vendor_image
   Backup_Display_Name: Vendor Image
   Storage_Path: /vendor_image
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/data | /dev/block/mmcblk0p62 | Size: 21916MB Used: 9887MB Free: 9730MB Backup Size: 9887MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
   Symlink_Path: /data/media/0
   Symlink_Mount_Point: /sdcard
   Primary_Block_Device: /dev/block/mmcblk0p62
   Crypto_Key_Location: footer
   Display_Name: Data
   Storage_Name: Internal Storage
   Backup_Path: /data
   Backup_Name: data
   Backup_Display_Name: Data
   Storage_Path: /data/media/0
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files
   MTP_Storage_ID: 65537

/cache | /dev/block/mmcblk0p57 | Size: 355MB Used: 0MB Free: 355MB Backup Size: 0MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p57
   Display_Name: Cache
   Storage_Name: Cache
   Backup_Path: /cache
   Backup_Name: cache
   Backup_Display_Name: Cache
   Storage_Path: /cache
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/cust | /dev/block/mmcblk0p61 | Size: 802MB Used: 298MB Free: 503MB Backup Size: 298MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p61
   Display_Name: Custom
   Storage_Name: Custom
   Backup_Path: /cust
   Backup_Name: cust
   Backup_Display_Name: Custom
   Storage_Path: /cust
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/misc | /dev/block/mmcblk0p30 | Size: 1MB
   Flags: IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p30
   Display_Name: misc
   Storage_Name: misc
   Backup_Path: /misc
   Backup_Name: misc
   Backup_Display_Name: misc
   Storage_Path: /misc
   Current_File_System: emmc
   Fstab_File_System: emmc
   Backup_Method: dd

/external_sd | /dev/block/mmcblk1p1 | Size: 30161MB Used: 11029MB Free: 19131MB Backup Size: 11029MB
   Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
   Primary_Block_Device: /dev/block/mmcblk1p1
   Display_Name: External SD
   Storage_Name: External SD
   Backup_Path: /external_sd
   Backup_Name: external_sd
   Backup_Display_Name: External SD
   Storage_Path: /external_sd
   Current_File_System: f2fs
   Fstab_File_System: vfat
   Backup_Method: files
   MTP_Storage_ID: 65538

I:Loading package: TWRP (/data/media/0/TWRP/theme/ui.zip)
I:Loading zip theme
I:Loading package: TWRP (/twres/ui.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/cz.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/de.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/el.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/es.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/fr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/hu.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/it.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/nl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_BR.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_PT.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/ru.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sk.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sv.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/tr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/uk.xml' directlyparsing languageFileparsing languageFile done
I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.791667x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Failed to load image from indeterminate013, error -1
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Including file: /twres/portrait.xml...
I:PageManager::LoadFileToBuffer loading filename: '/twres/portrait.xml' directly
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page flash_sleep_and_reboot
I:Loading page flashimage_confirm
I:Loading page clear_vars
I:Loading page reboot_system_routine
I:Loading page confirm_action
I:Loading page action_page
I:Loading page singleaction_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page appcheck
I:Loading page wipe
I:Loading page advancedwipe
I:Loading page formatdata
I:Loading page formatdata_confirm
I:Loading page checkpartitionlist
I:Loading page partitionoptions
I:Loading page refreshfilesystem
I:Loading page selectfilesystem
I:Loading page backup
I:Loading page backup_options
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backupencryption
I:Loading page backupencryption2
I:Loading page checkbackuppassword
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Loading page restore_read
I:Loading page restore_decrypt
I:Loading page try_restore_decrypt
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page system_readonly_check
I:Loading page reboot
I:Loading page rebootapp
I:Loading page system_readonly
I:Loading page settings
I:Loading page settings_timezone
I:Loading page settings_screen
I:Loading page settings_vibration
I:Loading page settings_language
I:Loading page copylog
I:Loading page advanced
I:Loading page partsdcardsel
I:Loading page partsdcardcheck
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page repackselect
I:Loading page repackconfirm
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageraction
I:Loading page decrypt
I:Loading page decrypt_pattern
I:Loading page trydecrypt
I:Loading page terminalcommand
I:Loading page sideload
I:Loading page fixcontexts
I:Loading page slideout
I:Loading page select_storage
I:Loading page select_language
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
Startup Commands:
ro.boottime.adbd=3507457029
ro.boottime.init=3078
ro.boottime.init.selinux=111
ro.boottime.init.cold_boot_wait=181
ro.boottime.logd=3484639790
ro.boottime.ueventd=3290798384
ro.boottime.qseecomd=3514871769
ro.boottime.recovery=3488612394
ro.boottime.keymaster-4-0=3581855571
ro.boottime.gatekeeper-1-0=3582846248
ro.boottime.servicemanager=3583835988
ro.boottime.set_permissive=3487782759
ro.boottime.hwservicemanager=3476452186
ro.config.ringtone=omni_ringtone1.ogg,omni_ringtone1.ogg
ro.config.alarm_alert=omni_alarm1.ogg
ro.config.notification_sound=omni_notification1.ogg
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
dalvik.vm.dexopt.secondary=true
dalvik.vm.usejit=true
dalvik.vm.lockprof.threshold=500
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.appimageformat=lz4
dalvik.vm.usejitprofiles=true
dalvik.vm.stack-trace-dir=/data/anr
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.image-dex2oat-filter=verify-at-runtime
dalvik.vm.dex2oat-minidebuginfo=true
debug.atrace.tags.enableflags=0
ro.art.hiddenapi.warning=1
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.opa.eligible_device=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.boot.dp=0x0
ro.boot.emmc=true
ro.boot.efuse=1
ro.boot.console=ttyMSM0
ro.boot.selinux=permissive
ro.boot.baseband=msm
ro.boot.configfs=true
ro.boot.dtbo_idx=6
ro.boot.hardware=qcom
ro.boot.keymaster=1
ro.boot.bootdevice=7824900.sdhci
ro.boot.secureboot=1
ro.boot.avb_version=1.1
ro.boot.usbconfigfs=true
ro.boot.verifiedbootstate=orange
ro.omni.device=olivelite
ro.omni.version=9-20191120-olivelite-HOMEMADE
ro.omni.version.security_patch=
ro.twrp.boot=1
ro.twrp.version=3.3.1-milankragujevic_9.0_v1
ro.vndk.lite=true
ro.vndk.version=28
ro.wifi.channels=
ro.allow.mock.location=1
ro.build.id=PQ3B.190801.002
ro.build.date=Wed Nov 20 16:49:01 CET 2019
ro.build.date.utc=1574264941
ro.build.host=milan-laptop
ro.build.tags=test-keys
ro.build.type=eng
ro.build.user=milan
ro.build.flavor=omni_olivelite-eng
ro.build.display.id=omni_olivelite-eng 9 PQ3B.190801.002 eng.milan.20191120.164901 test-keys
ro.build.product=olivelite
ro.build.selinux=1
ro.build.version.sdk=28
ro.build.version.base_os=
ro.build.version.release=9
ro.build.version.codename=REL
ro.build.version.incremental=eng.milan.20191120.164901
ro.build.version.preview_sdk=0
ro.build.version.all_codenames=REL
ro.build.version.security_patch=2099-12-31
ro.build.version.min_supported_target_sdk=17
ro.build.description=omni_olivelite-eng 9 PQ3B.190801.002 eng.milan.20191120.164901 test-keys
ro.build.characteristics=default
ro.bionic.ld.warning=1
ro.kernel.android.checkjni=1
ro.secure=0
ro.treble.enabled=true
ro.zygote=zygote32
ro.product.cpu.abi=armeabi
ro.product.cpu.abilist=armeabi
ro.product.cpu.abilist32=armeabi
ro.product.cpu.abilist64=
ro.product.name=omni_olivelite
ro.product.brand=Xiaomi
ro.product.model=Redmi (A
ro.product.device=olivelite
ro.product.locale=en-US
ro.product.manufacturer=Xiaomi
ro.baseband=msm
ro.bootmode=unknown
ro.hardware=qcom
ro.revision=0
ro.services.whitelist.packagelist=com.google.android.gms
ro.bootimage.build.date=Wed Nov 20 16:49:01 CET 2019
ro.bootimage.build.date.utc=1574264941
ro.bootimage.build.fingerprint=Xiaomi/omni_olivelite/olivelite:9/PQ3B.190801.002/milan11201649:eng/test-keys
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=OmniROM-9-20191120-olivelite-HOMEMADE
ro.setupwizard.enterprise_mode=1
ro.property_service.version=2
ro.control_privapp_permissions=enforce
ro.actionable_compatible_property.enabled=false
init.svc.adbd=running
init.svc.logd=running
init.svc.ueventd=running
init.svc.qseecomd=running
init.svc.recovery=running
init.svc.keymaster-4-0=running
init.svc.gatekeeper-1-0=running
init.svc.servicemanager=running
init.svc.set_permissive=stopped
init.svc.hwservicemanager=running
twrp.crash_counter=0
twrp.action_complete=0
crypto.ready=1
tombstoned.max_tombstone_count=50
sys.usb.ffs.ready=1
ro.build.fingerprint=Xiaomi/omni_olivelite/olivelite:9/PQ3B.190801.002/milan11201649:eng/test-keys
hwservicemanager.ready=true
log.tag.stats_log=I
ro.logd.size.stats=64K
ro.persistent_properties.ready=true
pm.dexopt.boot=extract
pm.dexopt.ab-ota=speed-profile
pm.dexopt.shared=speed
pm.dexopt.install=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.first-boot=extract
ro.boot.serialno=39b2a4210606
ro.serialno=39b2a4210606
service.adb.root=1
net.bt.name=Android
net.tethering.noprovisioning=true
sys.usb.state=mtp,adb
sys.usb.controller=msm_hsusb
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib.2=libart.so
persist.sys.disable_rescue=true
sys.usb.config=mtp,adb
ro.vendor.build.security_patch=2099-12-31
vendor.sys.listeners.registered=true
ro.crypto.type=file
ro.crypto.state=encrypted

SELinux contexts loaded from /file_contexts
Full SELinux support is present.
tw_get_context got selinux context: u:object_r:media_rw_data_file:s0
I:Got default contexts and file mode for storage files.
I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-05-31--06-29-29
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: no ats files found, leaving untouched!
I:Copied file /cache/recovery/log.gz to /cache/recovery/last_log.gz
I:Attempt to load settings from settings file...
I:InfoManager file '/data/media/0/TWRP/.twrps' not found.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Mount: Unable to find partition for path '/etc'
I:Copied file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/Redmi_A'
I:Starting MTP
I:sending message to add 65537 '/data/media/0' 'Internal Storage'
I:Message sent, add storage ID: 65537 '/data/media/0'
I:sending message to add 65538 '/external_sd' 'Micro SD card'
I:Message sent, add storage ID: 65538 '/external_sd'
MTP Enabled
I:[MTP] Starting MTP
I:Switching packages (TWRP)
I:Set page: 'system_readonly'
I:[MTP] created new mtpserver object
I:[MTP] mtppipe add storage 65537 '/data/media/0'
E:[MTP] Failed to start usb driver!I:[MTP] mtppipe add storage 65538 '/external_sd'
I:operation_start: 'Toggle System Mount'
I:operation_end - status=0
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
I:Starting Adb Backup FIFO
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Set page: 'advanced'
I:Set page: 'filemanagerlist'
I:Set page: 'filemanageroptions'
I:Set page: 'filemanagerlist'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
E:[MTP] request read returned -1, errno: 5I:Set page: 'install'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 2047
I:Set overlay: ''
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0

decryption relies on rom and firmware, in your case FBE uses login credentials from /data/misc/keystore and /data/system/locksettings.db you must restore and flash the matching system vendor modem etc

The syntax for decrypting TWRP from a command prompt is from a root shell or with TWRP a shell in general. Like: decrypt password :
 # decrypt /data with provided password Specific pattern decrypt note
Use the table bellow to determine what your password will be: pattern logic here: https://twrp.me/faq/openrecoveryscript.html
Example: if your pattern is a "U" shape in the middle of the 5x5, enter twrp decrypt '7<ABC>9' in the terminal or ADB shell. Note that characters ;<>? are special to the shell and require backslash escaping or single quotes around the string.

Heyya thanks again.  I have /vendor /recovery  etc backed up from stock because even for custom rom they wont change ( backed up stock after TWRP Nandroid backup ) . I did restore /recovery /boot from  previous Nandroid and the phone will still hang on boot logo. I dont have /system and /data backed up for this custom ROM.But TWRP is concerned with recovery so if I re-installed TWRP how do did that put me in a  boot logo freeze. Also of course I tried the TWRP decrypt command line thing using TWRP's guide nothing worked.

That'd had needed PIN + Key and something ran amuck on the key after TWRP reinstall Anyway a DD copy is of no use unless the data is decrypted and it wont backup via Nandroid either. Had to let it go

I was in a similar issue on a Nokia running a stock ROM. Basically Magisk module killed my phone and the TWRP won't allow decryption.
I was able to boot successfully to system again by.. Removing Magisk, because in the absence of Magisk, the Magisk modules shouldn't load and hence the system should boot just fine. I did that by flashing my stock boot image. Then I took a backup and did a reset.
You didn't specify which device you're using. But on an A/B device you can flash your original boot image from Havoc (from the exact same build you're currently on -- in case you installed any updates) on the active boot slot (double check that the boot slot didn't change while phone was trying to boot and fell back to the other slot when the active couldn't boot.
For the boot image, it is important for it to be from the exact same build, except the mismatched "Android OS level and OS version" can cause the phone to not boot.

Thanks for wanting to help @Singh. Just updated my Q w comments I am on Redmi 8a

@user1874594 I couldn't figure out if the Redmi 8A is a project treble device and if it supports A/B partitions. Google is a tough place to find such info. You should still try booting your boot image from Havoc (matching the exact version that is currently installed on your phone) using - fastboot boot . If the boot image matches and the system is still capable of booting, it should go into Android system.

Redmi 8A is a project treble device yes. ' booting your boot image from Havoc' do you mean installation of Havoc again . I have a system image of havoc. that will sit in /system. I can install that via Recovrey. Oh and yes my previous Nandroid stock rom back up. I installed  /recovery from there. I didnt try /boot - would that help ?

@singhnsk Magisk will destroy FBE because there is no way to disable forceencrypt. unfortunately topjohnwu decided to destroy FDE also, if you want to disable forceencrypt for FDE you must use Magisk Manager v7.3.4. same bug is true for Zackptg5's Disable_Dm-Verity_ForceEncrypt

Howdy 'gain Alecxs. . To take home something - can I get access to decrypted  data ? ..should I Nandroid /data  ? and format proceed with rest OR there's nothing that can be done and I should save the sweat ---> format /data and do a fresh OS ?

how about this link https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228  how could this be done when your backup itself is  encrypted

the backup itself is of course unencrypted. you can't create backup on encrypted undecrypted device. Your only chance left is to restore all necessary partitions like it was before

ok then its a dead horse - clean slate. Wish I had nandroided everytime I thought on going on an adventure. The only thing between non booting ( stuck logo) OS and booting OS was that TWRP re-install. What Happened ? does TWRP  reinstall  mess with the meta partition that stores the encrypted key. I am posting the recovery log if that helps tell a story for anyone whom this may help .


text:
Windows can access the phone's internal storage over USB, but not it's Micro sD card
My Samsung Galaxy A8+ (A730F), running Android Pie, had a faulty USB connector due to water damage and for a very long time, it wouldn't connect over USB. Nevertheless, everything else worked just fine.
Recently I had this piece replaced by a technician and it seems to be working alright, but I just noticed that on Windows, my 128GB micro SD card is shown next to my Internal Storage as empty and with a size of 128MB.
I can interact normally with the Internal Storage and when I put the micro SD card in a card adapter and plug it on my PC, everything works fine.
I'm using and original USB cable, my micro SD card is legitimate (confirmed it on SanDisk's website) and there aren't any other issues. Also, I have root access.
I tried clearing cache/data on Media Storage and External Storage, but had no luck.
I know that if nothing helps, I'll have to contact the technician, but I'd like to discard other possibilities first.
Any tips?
Thank you!

Try different ports on laptop /USB cables to see if that helps?

Did it, the problem is still there :/

Which file-system is used by the external micro-sd card? Have you performed a file-system check if the file-system itself has problems?

I happened to have another phone of the exact same model and another micro SD card for testing. Every combination of ports, cables and cards worked with the other phone, but did not with mine, so the problem is definitely on my phone!


text:
Folders become unknown, undeleteable file type. How to fix and/or delete?
I'm trying to re-organize and replace the music on my phone's ext. SD card, but some of the folders have become some sort of unknown file type. In Windows, the properties window just says it's file type is "File". That's it.
I can't delete, open, or move them (from my PC or in the phone itself); however, I can still listen to the music (only through my music player app) and rename the folders. I've tried deleting them in Windows, in my phone's music player app, and in my phone's file manager but nothing seems to work; on Windows it says,

[Album name] could not be deleted. The device has either stopped responding or has been disconnected.

and on my phone deleting it does nothing and gives no feedback whatsoever.
Is there any way to fix this? I'm okay with deleting the files since I have more copies, but that doesn't seem to be possible either. I would probably be okay with most options except nuking the entire SD card
Thank you in advance.

You should reboot your phone. Android re-scans the sd-card after the reboot. Hopefully this fixes the consistency issues you see.

@Robert I've rebooted multiple times and they're still like that. One day they were normal folders, and now they're just "Files" — it doesn't switch between or anything. So I don't think this is a consistency issue; they changed, but they're not changing back on their own.


text:
How do I find out when I will be able to change country in play store again?
I know I can only change once per year, I but I don't remember when I last changed it. I think it was close to a year ago, but I would like to be able to see what date the 1 year will expire so I can set a reminder then to go and change my country.
p.s. why is this once per year restriction in place? is it a legal thing or a commercial thing? Does not make sense to me.

Good question and I couldn't find an answer. Maybe Google intimated to you by mail after you changed. Did you check your profile using web browser - maybe it's mentioned there. Easiest thing would be from Play Store settings go to help and feedback and mail them. Regarding your PS-we can't answer that, we aren't Google

I would assume that the country change restriction exists to allow regional offers. If anybody could simply switch the country at any time to get a certain regional offer such offers would not make much sense anymore. Hence I would assume the reason if commercial. Of course this also simplifies the tax calculations per user (and enhances the chance that the taxes are collected for the correct country).


text:
Hard Reset on SAMSUNG TAB 4 SM T230NU not working. What are the alternatives?
I have a SAMSUNG TAB 4 SM T230NU. Don't remember the password. I tried the Hard Reset of
1) Menu(Home) + Power + Volume Up buttons
2)  Power + Volume Up buttons
Each time I try one of the above sequence, I see that the system powers on and I see the initial samsung logo with the model name. After a few seconds, the screen empties and then again, the same samsung logo with the model name. This sequence repeats.
But I never see the RESET Menu.
What did I get wrong ?
Isn't there a way to get a password reset instruction in the email that I've setup ? For example, how do I get to a "Forgot password" screen/button ?
Thank you

It's not clear if you performed reset as detailed

yes, I did as detailed!

That's not the problem then. Hope Samsung users can help out. All the best


text:
Activate alarm, ringtone or audio using ADB?
I have misplaced a junker phone (LG G3 running Lineage).  However, it's still on, and ADB is accessible over TCP/IP.  (The phone doesn't have a SIM, so I can't call it.)
Is there a way to turn on the ringer or other audio from ADB?  I've tried a couple of remote-screen apps (adb-remote-control.jar and scrcpy) but although they appear to connect, and scrcpy even gets a screen image that looks correct, neither of them seem to send events correctly, so I can't control the phone.
I suspect there's a way to launch an app (Phone?  Alarm?) with a "Play Ringtone" intent, but I don't know how.

Suggestion of Google find my phone
worked: Google knows where your phone is, even if you don't.
From another user, you can also do it with ADB:
adb push t.mp3 /sdcard/
adb shell am start -a android.intent.action.VIEW -d file:///sdcard/t.mp3 -t audio/mp3

(Playing a video file the same way or starting youtube (adb shell am
  start -a android.intent.action.VIEW -d
  https://www.youtube.com/watch\?v\=oVQqmH4ufCQ)) will not produce any
  sound if the device is locked it seems like)

This pops up a player. Is it possible to play back a file without GUI?


text:
Recompile kernel: no errors but it doesn't work
I'm a beginner, and at the moment I'm trying just to repack original boot image. I've discovered that boot partition is on the "/dev/block/mmcblk0p7", so I pulled it with adb pull /dev/block/mmcblk0p7 original_boot.img
Then with tools from https://forum.xda-developers.com/showthread.php?t=2319018 I've unpacked original boot and then recompiled it. But then my image don't boot. Flashing it with TWRP caused bootloop. Where am I wrong?

Kinda close to off topic but I do not think so. My reasoning is because it has to do with repacking a boot image and not the compilation of the kernel. Also, I found a possible duplicate with this https://android.stackexchange.com/questions/69954/how-to-unpack-and-edit-boot-img-for-rom-porting check the compression also. How arw you repacking the boot.img?

@BoLawson I don't think its a duplicate. First, I've unpack original_boot.img then used the command which  Boot.img tools provided when unpacked: mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x4dffff00 --cmdline 'bootopt=64S3,32N2,64N2' --board '1450664547' -o new_boot.img

Use AIK

@IrfanLatif same result


text:
Why is the proximity sensor suddenly shining brightly?
Top right is where the "light / proximity sensor" lives, according to the manual. It is clearly visible as white light on this photo - that is expected. What is NOT expected is that it is also clearly visible to the naked eye?! It's a tiny red dot, impossible to photograph as such.
That sensor has never been visible before! Why is it visible now?

I don't find it unusual that this sensor is active. Are you sure the red dot was not visible before? May be it was just so dark that you did not notice it?

The sensor is probably always active. But it has never been visible, and indeed is not visible on any of my other phones. This is visible in normal indoor lighting. The sensor uses infrared which is not visible to the human eye and I am sure I did not suddenly develop weird super powers.

It is light/proximity sensor as per details highlighted.light sensor is supposed to measure ambient light. I don't know why it is so clearly visible but a couple of things to try - go into sunlight or bright light stay there for a while and come back indoors to check, check if selfie camera is on, toggle auto brightness

@TorbenGundtofte-Bruun From what I found, that might be the front facing selfie flash. Double check your tile settings or perhaps a third party app is turning it on/left on.

Does the proximity and light sensor still work? Use a sensor app to test. May be the receiver part of the sensor does not work anymore and therefore causes the ir led to be constantly active.

@MorrisonChang it's not the front flash, see the feature chart (third image).

You can check if the light sensor is working fine, using this app. More on Play Store, I just picked up well rated