text:
On a non-rooted device, can adb access any files that an Android file manager cannot?
An Android app I was relying on did not save its data.  I'm hoping that perhaps the data is located in a cache or temporary file.
The device is not rooted (and is running Android 7.0), and I've scoured all storage accessible without root using a couple different file managers.  Neither found anything of interest.
Using adb, is it possible to see more data on a non-rooted device than a file manager can inspect?
If not, is there another technique to accomplish this?

Update:
More specific details were requested, so they are presented here:
I was using the Mega Call Recorder Advanced Android app to record phone calls.  At the end of a critical call, I went to copy the recording to a backup device.  The call was not present in the list of recordings.  Of course, that doesn't mean the call wasn't recorded by the app; it just means the final recording did not make it into its output folder (which does happen sometimes with that app). It is possible that the recording is stored in a cache or temporary file somewhere on the device.

The answer is yes... But if your comparing it to root it's likely not what your looking for. If you would be more specific as to what you are trying to accomplish, we may be able to assist you.

As I see it, the only hope you have is to use adb backup for that app. This can work only if your app allows its data to be backed up. Otherwise, you are done for.

@acejavelin Thank you for your request for more details.  I have added them to the question.

Have you tried something like Solid Explorer and enable it's root file system? It doesn't require root to read most things, although you will get a few security prompts. I am not familiar with this app but in general apps only get access, even temporarily, to their own directories, so look in areas like the Android/data/{app} folder. Apps don't usually get access to "temp" or cache storage directly, but it maybe a partial file in it's own folders.

@acejavelin I took a look using Solid Explorer (SE).  There is no Android folder reported in the root, but there is a data folder.  When I click on the data folder, SE reports Unable to browse the directory under "/data"..  Did I follow your instructions correctly?

if app is debuggable you can access /data/data/pkgname from adb run-as

@alecxs Thanks.  When adb was first released, I used it quite a bit, but I haven't used it very much in recent years.  How do you determine if app is debuggable, and if it is, what adb command would be used to access /data/data?

@alecxs What's your fax number? I'll fax you a cup of coffee.  ;)

@alecxs Done. Now I have two cups. ;)

@Firelord In reading the official ADB documentation (https://developer.android.com/studio/command-line/adb), I'm not seeing adb backup.  Do you have a good official reference for that command?  I found https://android.stackexchange.com/questions/28296/how-to-fully-backup-non-rooted-devices, but that's unofficial and the info is almost a decade old.

@RockPaperLz-MaskitorCasket that linked question has relevant answers, despite their age.

is your device mediatek chipset? https://android.stackexchange.com/q/219346

https://android.stackexchange.com/q/48609
https://android.stackexchange.com/q/182403

@alecxs No problem.  I just took a look and left a comment.  I also upvoted your question so Roomba doesn't eventually delete it. :)


text:
How can I take a picture with the depth camera?
Many phones - such as my Nokia 7.1 - now come with depth cameras and other auxiliary cameras built-in.
For example, my Nokia 7.1 has a front & back facing camera as you might expect, but also has a depth camera listed in the specifications:

(link to full specs)
With this in mind, I'd like to be able to take a picture with the depth camera on my phone. Unfortunately though, it doesn't show up if I press the switch camera button in the default camera app - that just switches between the front and back facing cameras.
I've also tried a 3rd party camera app (Open Camera) to no effect.
How can I take a picture with the depth camera directly, and save it as a JPEG file?

Ah, I see @Robert. If nobody else answers, then I'm happy to accept that as the answer to my question for now. It's still a valid answer - even if it's saying that it's not possible....

While the Nokia 7.1 has a 'depth' camera. It is unclear if the 5MP camera has been exposed to developers (doubtful) or is part of the overall camera system for image enhancement (more likely).
On the other hand a phone like Samsung S10 5G does have a 0.3 MP, TOF 3D, (depth) sensor accessible to Android app developers.
When referring to depth, its not an hi-res image that a user can look at, but a feature that a camera app developer can take advantage of when the hardware supports it.
For Android developers in the Camera2 API there is REQUEST_AVAILABLE_CAPABILITIES_DEPTH_OUTPUT
Which uses DEPTH16 Android Image format.
For the more technically inclined there is a Medium post on Working with the 3D Camera on the Samsung S10 5G where the author goes into how to use the 3D camera data.
A key point from the article is that the resolution of the DOF is much lower than any visible light image.

The ToF Camera
The front-facing ToF sensor on the Samsung S10 5G is a Sony IMX316. It outputs frames in the DEPTH16 image format with a resolution of 240x180. It has a 75° field of view, which roughly matches the S10 5G’s front-facing camera’s field of view of 80°.

As you can see in the article, the author is using the depth of field image data for bokeh or background blur as each pixel is a depth value and a confidence level. The author also has to apply a variety of techniques to the DEPTH16 data as it appear to be quite noisy.
Those so inclined can get the author's source code here: https://github.com/plluke/tof

source: Stack Exchange

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

sort: votes


text:
adb install-multiple fails with error: [INSTALL_FAILED_INVALID_APK: Split null was defined multiple times]
I'm trying to install multiple .apk files to my Samsung Note 4, over adb. I'm able to install the same set of files individually using the 'install' command, but when I try to 'install-multiple' I get the following error:
adb: failed to finalize session
Failure [INSTALL_FAILED_INVALID_APK: Split null was defined multiple times]

All my own research on the error turns up issues relating to development, but nothing relating to simply installing some .apks. The actual files do not have any spaces or special characters in their names. When I run the command with tracing enabled, you can see that the command that is actually being executed after expansion is syntactically correct.
adb install-multiple /tmp/update_phone/*
+ adb install-multiple /tmp/update_phone/firefox.apk /tmp/update_phone/protonmail.apk /tmp/update_phone/protonvpn.apk /tmp/update_phone/whatsapp.apk

Any advice would be heartily appreciated!
Ubuntu 20.04 | adb version 1.0.39 | Samsung Galaxy Note 4 | Lineage OS 17.1

I think what you want to do is Batch install apks from computer to Android without actually touching my Android. adb install-multiple is for installing split APKs (single app, multiple APKs), not multiple different apps.

Thank you very much @AndrewT. The adb documentation doesn't make this clear at all, but now I know.

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


text:
Moto G5 will not boot, what are my options to recover user data?
I have a Moto G5 (XT1676), which is stuck in a boot loop. It will ask for my pattern to unlock the partition, and then the motorola / lenovo logo spins forever and the phone will not boot.
What are my options to recover the user data ?
I am able to access the recovery, and I have tried already tried to clear the cache partition, with no luck. There is no option to backup the user partition in the stock recovery.
I could flash TWRP recovery and backup the phone from here, but my booloader is OEM locked, and unlocking it requires wiping the phone.
Is there a way to unlock the bootloader without wiping the phone ?
Or is there a way to backup the user partition from the stock recovery ?

Moto G4 is listed as exploitable, maybe works similar https://blog.elcomsoft.com/2018/05/demystifying-android-physical-acquisition

read/flash partitions without losing data may possible, only encryption is showstopper usually (but your pattern still works?) maybe you can enable adb or root by slightly modifying boot.img (on locked bootloader) depends on AVB version https://android.stackexchange.com/q/227110

romprovider.com, firmware27.com, leakite.com, github.com, tuserhp.com, firmwarego.com

I was able to make my phone boot again by flashing a stock (official) firmware, without erasing the userdata partition. As it uses an official firmware, this approach does not require unlocking the bootloader. Here is a summary of the steps I followed.
Install fastboot
Fastboot is an utility that is used to upload and flash ROMs on Android Smartphones.
On Linux, fastboot can be downloaded as follows:
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip platform-tools_r31.0.0-linux.zip
# Using fastboot requires root permissions, so from now on
# we execute commands as root
sudo -s
export $PATH=$PATH:/path/to/platfrom-tools

For other OSes, you may find installation instructions here:

Using ADB and fastboot - LineageOS Wiki
Minimal ADB and fastboot - XDA Developers

Start the Moto G5 bootloader
To do so, shutdown you phone. Then press Volume down and Power
Plug the USB cable in, your phone should now appear when you type:
 # fastboot devices
 ZY3222HM8L Motorola Fastboot Interface

Find an official ROM for your phone
This is definitely the most risky and tricky part, as there is no foolproof way to determine which is the good ROM for your phone.
The least risky way is to use the Lenovo Rescue and Smart Assistant (LMSA) to download the ROM for your phone. However, DO NOT USE LMSA TO FLASH YOUR PHONE, IT WILL ERASE YOUR DATA.
Use LMSA to download the ROM, locate the zip archive it downloaded, and close it. LMSA requires Microsoft Windows, so this is not a viable solution for Linux users or MacOS users.
The other solution is to guess which ROM is appropriate for your phone, and download it from a public mirror. I used: https://mirrors.lolinet.com/firmware/moto/cedric/official/. Identify your model variant by looking at the information displayed by the bootloader. The important line is:
 Product/Variant: cedric XT1676 16GB P5

Try to explore the "RETAIL", "RETEU" (Retail EU), "RETUS" (Retail US) etc. depending on your country and try to find a an archive that matches your phone variant. Mine was in RETEU:
 XT1676_CEDRIC_RETEU_DS_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Make sure you download the last version for your phone (look at the dates, and version number 19-4-2) because the bootloader will not allow you to downgrade your OS.
Flash the ROM on your phone
Unzip the archive you just downloaded, then locate the flashfile.xml file. Open it with a text editor, and locate the <steps> block
<step operation="oem" var="fb_mode_set"/>
<step MD5="9f3a13b8222b08e2171d2519e5276c31" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="9ea732d853c838d9ed8486ca6df10321" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="3605a87a6e4ba36c2f995204a7ec2aa6" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="77aec885e43c1441ae775a36add08125" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="bded198b6f1d31e9ce664376503b223b" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="0f114b5a2ab83e18444fa0d8e79a8e0e" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="4559fd8bad5404d1ec16a98614b3765a" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="864a8060abe29e56fe2e8e93cac2c4a3" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="39b15d4e645ba9576e819edfaf5b668e" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="ed64b41d92f7cf5f4079442fc446e0af" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="aef832b70ded5b7b5788bf87b61a8ad6" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="31c52fe5f412ac621e325f879a08e6e8" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="982e8d23a01a1017c72c23c56aed3ca2" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="1ef6cd540e95e3fe2c80d934376b6f3a" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="66a2a34e2bacd1ab0f5065524e2ce141" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="052ca5a46c322450dacad5678c31ac0e" filename="system.img_sparsechunk.7" operation="flash" partition="system"/>
<step MD5="0a20486510c1c5f45d1d8dbfcf0b9975" filename="system.img_sparsechunk.8" operation="flash" partition="system"/>
<step MD5="1e60bbc27184845acdc99d789f503c0c" filename="oem.img" operation="flash" partition="oem"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>

Then translate each step into a flashboot command, and write a script. However DO NOT TRANSLATE THE ERASE USERDATA AND ERASE DDR commands. In my case the script I wrote was as follows:
cat fastboot.sh
set -x
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase clogo

Again, make sure THERE IS NO erase userdata line.
Make sure your phone is plugged securely, then you may then execute this script as root. It will flash your phone with the official ROM.
Once this is done, use the volume up and down keys on your phone to navigate to the "Start" entry and press power. Your phone should reboot, and hopefully your userdata partition will still be there.


text:
What is com.hmdglobal.app.customizationclient.OTAApplication?
I keep receiving an error about the app "com.hmdglobal.app.customizationclient.OTAApplication" crashing on my Nokia 2.2. What does this app do?
The app can't be uninstalled and can't be disabled, and has full access to call logs, phone and storage. Based on the name, I presume it's created by Nokia to harvest my personal data.
Am I being paranoid or is this app malicious in any way?

Based on the package name I would assume that this is the app that searches in background for system updates for your phone (OTA = Over The Air updates).

I have had the same problem on my Nokia 4.2 for the last few days (since approximately 2021-03-04). Since our devices were both released in the spring of 2019, I wonder whether that sadly means they no longer qualify for Android updates? EDIT: Scrap that, there's a report on the XDA forum of the same thing on a Nokia 5.4. So probably just a bug.


text:
Possible to activate security screen lock only when out-of-home (out-of-specific WIFI )?
I am quite a critic of every system which does not give a customization abilities. One of them is the frustration of using the security behaviors of phone - specifically, some of use have some of us lock the phone with either Pin-Code or Pattern or Fingerprint or whatever, having phone at home, and unlocking screen hundreds of times a day for no reason, is just out-of-any borders of convenience.
So, i've been thinking, what technical challenges or problems there were, which interfered the developers to implement a relatively easy (not a rocket science) solution, to have "enabled that lock" security mechanism, when we leave home (or specific WiFi) area?  So, at home, we wouldn't need to waste extra ~3 seconds everytime we unlock phone (maybe it's nothing for you, but in sum every day, it is inconvenient for me).

Check our device for "Smart Lock".

Does this answer your question? Android Smart Lock: Why is there no option to use WiFi?. See all answers


text:
How do you pair a Device for Wireless Debugging with a QR Code?
There doesn't seem to be much written on this, but I see an option to pair my device with a QR code scanner. Is there a way to pair my phone with my computer by generating a QR code on my computer and scanning it from my phone?
I'm running Ubuntu 20.04.
I'm using the Pixel 4a running Android 11.

This answer explains the background history of the built-in feature in Android Studio. For the technology used and 3rd-party software, you can read my answer here.

As of 26 January 2022, the feature can be used on the stable version of Android Studio Bumblebee 2021.1.1 with Android 11+ devices. Though, the performance may still be buggy on some platforms.
Background History
While the revamped wireless debugging has been known since

the source code commits in October 2019 by XDA

On the user-side, Google plans to add a new “wireless debugging” switch in Developer Options that supports pairing devices by scanning a QR code or entering a 6 digit code.

the release of Android 11 DP2 in March 2020, as reported by 9 to 5 Google and Android Police

it was first introduced officially on Android 11: Developer Preview 3 in April 2020.

Wireless Debugging - In Android 11, we’ve completely revamped the debugging experience using ADB over a Wi-Fi connection. With limited USB ports on laptops, and a myriad of USB cables & connections to manage, the Wireless Debugging feature in Android 11 can help you be more productive. Unlike the existing TCP/IP debugging workflow, Wireless Debugging on Android 11 does not need a cable to set up, remembers connections over time, and can utilize the full speed of the latest Wi-Fi standards. In DP3, use the pairing code workflow to get started with this developer feature. We plan to add an integrated experience for Wireless Debugging with QR code scanning in a future Android Studio release, but we want to get your early feedback on the command line tool offered in Android 11 DP3. For details, see the documentation.
(Emphasis added, link fixed)

However, it was not until December 2020 that the new Android Studio Canary version, Android Studio Arctic Fox (2020.3.1) shown the pairing interface for the first time.

Lastly, for those running MacOS (other platforms are coming soon) with the latest Android Platform tools and an Android 11 device, you can try out the IDE integration for the Wireless ADB feature by going to the Run device selection dialogue → Pair Devices Using Wi-Fi.

Menu to access Wireless ADB feature

Wireless ADB Setup Window

That's pretty cool. I use adb on the command line so I was half expecting some ncurses based qr code generation thing haha. Maybe in the future who knows.

I found out in the meantime that you need to use the ’adb pair’ to pair, but it's guess you can do this just by using a USB cable too. When paired you can use ‘adb connect‘ to connect the device.

You can pair your phone wirelessly using ADB by following these steps:

Make sure your phone and laptop are on the same network.
Open the following menu on your phone: Settings>Developer options>Wireless debugging. Enable the feature and then click on Pair device with pairing code on the same screen.
Open a terminal on your laptop and use the below command to pair your phone with your laptop:

adb pair host:port code

You can find host, port and code on your phone screen after clicking on Pair device with pairing code in the wireless debugging menu.
4. Run the below command to make sure the pairing has been done successfully:
adb devices

I appreciate the answer, but that wasn't my question. The question has to do with the fact that there is a way to pair a phone using a QR code and I was wondering how you could do that instead of using the code.

appreciate this was not what the OP was looking for, but I came here via Google and this was exactly what was needed.

After doing adb pair, you also need to adb connect host:port. The connect port is not the same as the pairing port (though the IP should be the same).

This answer explains the technology used and 3rd-party software. For background history of the built-in feature in Android Studio, you can read my answer here.

Android 11 and ADB utilize multicast DNS (mDNS) for its wireless pairing.
ADB 30.0.0 added support for wireless pairing, including commands like:

adb pair to pair the Android device with the host machine using pairing code

adb mdns check to check which mDNS daemon is used

On Windows, using Openscreen discovery added in ADB 31.0.2:
C:\android-sdk\platform-tools> adb mdns check
mdns daemon version [Openscreen discovery 0.0.0]

On Windows, using Bonjour service
C:\android-sdk\platform-tools> adb mdns check
mdns daemon version [2140303]

adb mdns services to list available mDNS services created by the Android devices
C:\android-sdk\platform-tools> adb mdns services
List of discovered mdns services
adb-941AY0HXWG-r8Nucn   _adb-tls-connect._tcp.  192.168.0.147:37387
adb-941AY0HXWG-r8Nucn   _adb-tls-pairing._tcp.  192.168.0.147:42885

In addition to the built-in feature in Android Studio, there is also some 3rd-party software that simulates the same process by generating a QR code to initiate the wireless pairing:

GitHub - benigumocom/debug_from_qr.py: an executable Python 3 script

Dependency packages:

zeroconf
qrencode

Windows executable: GitHub - valterfukuoka
/
qrencodecompilewindows

Demo video: YouTube - BENIGUMO.COM - Pair device with QR code - Android11

Sample
C:\> py .\debug_from_qr.py
█████████████████████████████████
█████████████████████████████████
████ ▄▄▄▄▄ █ ██▀▀ █ ▀█ ▄▄▄▄▄ ████
████ █   █ █  ▀█▄█▄▀▄█ █   █ ████
████ █▄▄▄█ █▀  █ ▄ ▄▄█ █▄▄▄█ ████
████▄▄▄▄▄▄▄█▄█ ▀▄▀ █▄█▄▄▄▄▄▄▄████
████ ▄██ ▄▄▀██▄▀▀▀ █ ▀█ █▄ ▄▄████
████▄▄▄▄▀▀▄▄▀ ▄█▄▄▀▄███▄▄████████
████ ▄▄ ▄█▄▀▀▀▀▀▀ ▄▀█▀▄▀▀ ▄▄▄████
██████▄█▀█▄▄ ▄██▄▄▀▄▄▄▀▄█▄▀▄▀████
████▄▄██▄█▄▄ ▄▀▀▄▀ ▀ ▄▄▄   ▀▀████
████ ▄▄▄▄▄ █▀▄█▄▄▄▀▄ █▄█  ▀██████
████ █   █ █▄ ███▀▄█ ▄▄  ▄▄▄ ████
████ █▄▄▄█ █▀▄█▄▄▄▀▀ ▄▄▄█▄▀ ▀████
████▄▄▄▄▄▄▄█▄█▄█▄▄█▄████▄▄██▄████
█████████████████████████████████
█████████████████████████████████
Scan QR code to pair new devices.
[Developer options]-[Wireless debugging]-[Pair device with QR code]
Press enter to exit...

Service debug._adb-tls-pairing._tcp.local. added.
service info: ServiceInfo(type='_adb-tls-pairing._tcp.local.', name='debug._adb-tls-pairing._tcp.local.', addresses=[b'\xc0\xa8\x00\x93', b'\xc0\xa8\x00\x9f'], port=40067, weight=0, priority=0, server='Android-2.local.', properties={}, interface_index=None)

adb pair Android-2.local.:40067 123456
Successfully paired to Android-2.local.:40067 [guid=adb-941AY0HXWG-r8Nucn]
Service debug._adb-tls-pairing._tcp.local. removed.
Press enter to exit...

List of devices attached
adb-941AY0HXWG-r8Nucn._adb-tls-connect._tcp. device product:sargo model:Pixel_3a device:sargo transport_id:3

GitHub - saleehk/adb-wifi: an NPM command line interface (CLI) tool

Install: npm i adb-wifi -g

Usage: adb-wifi

Sample
C:\> adb-wifi
[Developer options]->[Wireless debugging]->[Pair device with QR code]
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ █▄▀ ▀ ▀ █▄▄█▄▀▄▄ ██ ▄▄▄▄▄ █
█ █   █ █   █▀  ▀▀█▄ █▀ ███ █   █ █
█ █▄▄▄█ █▄█▀ ▄█▀▄█▄▄ █ ██▀█ █▄▄▄█ █
█▄▄▄▄▄▄▄█▄█ █ █ █▄▀▄█ █▄▀▄█▄▄▄▄▄▄▄█
█  ▄▄▀▀▄█▄█ ▄   ▄▀ ██  ██▄▄██▄▄▄▀ █
█▀▀▀▀▄▀▄▄▄  ▄▄▀▄▀▀███▄█▄▄▀▀ ▀▀ ▄█▄█
█▄▀ █▄▀▄█▀ ▄▀ ▄▄▄▀█▀▄▄▀ ▄  ▀ █▄▄█ █
█▀ ██ ▀▄ ▀▀▀ █▄▀█ ▄▄ █ ▄▀ ▀  ▄█▀█▀█
██▄ ▄█▀▄█▄▀▄█▄ ▀▄█▀▄ ▀   ▀▄▄▀▀█  ▄█
█▄▀▄▄  ▄▀█  ▀█▄▀▄ ▀ ▀ █ ▀█ █▄ ██ ▀█
█ █▄ ▄▀▄ █  ██ ▄█▀▄▄▄▀   ███ ██▀▄▄█
██▀▄██▄▄ ▄ █▀▀ ▄█▄▄▄█ ██  ██▄ ▀█▄ █
█▄█▄█▄▄▄▄ ▀█ ▄▀▄▄ ▀█▀  ▄▄ ▄▄▄ █▄ ▀█
█ ▄▄▄▄▄ ██ ▀▀ █ ▀▀▄▀▄▄▀▀▀ █▄█ ▀▀▀██
█ █   █ █▀ ▄▀▄▄█▄█▀▄█▀▀  ▄▄▄  ▄█ ▄█
█ █▄▄▄█ █ █▄██▄█▄▄▀▀█▄▄▄▀█▀▀▀▀▀█▄▀█
█▄▄▄▄▄▄▄█▄██▄▄██▄█▄███▄█▄█▄▄██▄▄███

stdout: Successfully paired to 192.168.0.147:38629 [guid=adb-941AY0HXWG-r8Nucn]

mDNS Compatibility
Since this feature depends on mDNS, different operating systems may have different compatibility:

Apple has a native implementation in iOS and macOS
Linux distros tend to implement mDNS through the Avahi daemon
Windows does not have a native implementation until Windows 10 (1703), but even then it may still fail:

User may need to install Apple's Bonjour Print Services
Super User - How to enable mDNS on Windows 10 build 17134?

Additional references:

XDA Developers - Android 11 may finally bring a proper, native Wireless ADB implementation
Android finally supports a basic networking feature: mDNS .local resolution

This should actually be the accepted answer, as it is the most detailed one with highest developer experience degree

Just wanted to add that if you try to scan the QR code directly from the camera, like on a Pixel by pointing it at the QR code and clicking the link, it won't work. You will get an error message that says "QR Code contains incorrect WiFi password". This error message is a red herring, it has nothing to do with the WiFi password, you just can't pair with the QR code by scanning it with the camera
Instead, like is mentioned in Yandirr's answer, you have to go to:
Settings --> System --> Developer options --> Wireless debugging (Yes you can click the text) --> Pair device with QR code
Then when you scan the QR code it should work. I think it's bad UI design that you have to click on the "Wireless debugging" text since it looks like that's just a single radio button to toggle the Wireless debugging option, but in actuality there's an entire sub-menu hidden behind it.


text:
Cant adopt sd card to internal on Huawei Y6 2018
Hi i have a huawei Y6 2018 and i cant adopt my sd card into internal. My phone is rooted and i used the app Root Essentials. It asked me to flash a Plugin (ASPlugin). I Tried to do that but i got the Error 1 i searched for soloutions and found out that you need to take the boot.img and flash it. When i took the magisk.zip and opend it there was no Boot.img. So i downloaded a Boot.img file from the internet and flashed that one. That worked so i tried to now flash the Plugin (ASPlugin) and there was the Error 1 again. I dont know what to do now. I would love to get some help, because my fone only has 16gb internal storage and it is annoying me. I am using a Sandisk 32GB with 98 mb/s.

Does this answer your question? Problem with a sdcard under Android 7.1.2 three partitions can not be mounted / used


text:
Application crashes and I cant figure out why
I am trying to run an android application on a chromebook (android 9), but every time I try to open it, it has a black screen, then crashes. I have tried the basic things, clearing cache, re-installing the application, resetting my device. I tried to use logcat to trace the crash (By running the adb logcat command)
Here is the logcat
03-05 13:39:31.836   863  1503 I ArcIntentHelperService: Handling org.chromium.arc.intent_helper.SET_IN_TOUCH_MODE from Chrome...
03-05 13:39:31.858   597  1034 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:899 android.content.ContextWrapper.startActivity:401 org.chromium.arc.applauncher.AppLauncherService.launchIntent:1869 org.chromium.arc.applauncher.AppLauncherService.launchAppWithWindowInfo:1826 org.chromium.arc.mojom.AppInstance_Internal$Stub.accept:1009
03-05 13:39:31.860   119   403 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity} from uid 1000
03-05 13:39:31.860   119   403 W ActivityManager: getValidLaunchStackOnDisplay: can't launch on displayId 0
03-05 13:39:31.868   119   403 I ActivityManagerInjector: getResolvedRootLaunchBounds called with root activity {N-unresizeable 0x0, AC, PropertyRecord{mVersion=3, mDisplayId=0, mBounds=Rect(0, 0 - 0, 0), mRestoreBounds=Rect(0, 0 - 0, 0), mWindowMode=1, mWasUserResized=false, mImmersive=false, mLastWindowStateInClamShell=-1, mWindowLayoutAffinity=10060:null}}
03-05 13:39:31.868   119   403 E WindowManagerInjectorArc: setArcAttributeWindowSizeConstraints: cannot find task: 19
03-05 13:39:31.868   119   403 I ActivityManagerInjectorArc: updateCaptionLocked: skipping activity that isn't fully started
03-05 13:39:31.872   119   403 I ActivityManagerInjectorArc: notifyActivityAddedToTask: added to new task. activity=ActivityRecord{df7a9b3 u0 com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity t19}
03-05 13:39:31.872    11    60 D wayland-service: Couldn't find a window for task_id 19, will set orientation lock when next added.
03-05 13:39:31.875   119   334 D DecorView[global]: Cannot get the activity to get CaptionConfiguration.
03-05 13:39:31.891   597  1034 I ArcAppLauncherService: Activity launched for Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity }.
03-05 13:39:31.896   119   334 D ArcInputCompatHandler: Using touchscreen emulation for all games.
03-05 13:39:31.948    11    11 D wayland-service: Creating app window for task_id 19 from package 'com.klab.lovelive.allstars.global'
03-05 13:39:31.949    11    11 I wayland-service: Set task 19 orientation lock from package 'com.klab.lovelive.allstars.global'
03-05 13:39:31.949    11    11 D wayland-service: Setting orientation lock to 3 for task_id 19.
03-05 13:39:31.949    11    11 I wayland-service: Set task 19 window type 1from package 'com.klab.lovelive.allstars.global
03-05 13:39:31.949    11    11 D wayland-service: ApplyBackgroundColor for task_id 19, color=-16777216
03-05 13:39:31.874   119   403 I ActivityManagerInjectorArc: notifyActivityAddedToTask: added to new task. activity=ActivityRecord{df7a9b3 u0 com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity t19}
03-05 13:39:31.958   119   403 D ActivityManagerInjectorArc: taskOcclusionChanged: taskId=19 does not support PIP
03-05 13:39:31.961   119   358 I InputDispatcher: Dropping event because there is no touchable window at (896, 479).
03-05 13:39:32.372   119   288 I OrientationSynchronizer: Setting rotation is timed out
03-05 13:39:32.373   119  2139 E ActivityManager: applyOptionsLocked: Unknown animationType=0
03-05 13:39:32.397   119   290 I ActivityManager: Start proc 5722:com.klab.lovelive.allstars.global/u0a60 for activity com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity
03-05 13:39:32.441  5722  5722 D houdini : [7508] Initialize library(version: 9.0.5c_z.51331 RELEASE)... successfully.
03-05 13:39:32.446  5722  5722 E allstars.globa: Not starting debugger since process cannot load the jdwp agent.
03-05 13:39:32.503    11   642 W SurfaceFlinger: Attempting to set client state on removed layer: org.chromium.arc.home/org.chromium.arc.home.HomeActivity#0
03-05 13:39:32.503    11   642 W SurfaceFlinger: Attempting to destroy on removed layer: org.chromium.arc.home/org.chromium.arc.home.HomeActivity#0
03-05 13:39:32.507    11   642 W SurfaceFlinger: Attempting to set client state on removed layer: org.chromium.arc.home/org.chromium.arc.home.HomeActivity#0
03-05 13:39:32.507    11   642 W SurfaceFlinger: Attempting to destroy on removed layer: org.chromium.arc.home/org.chromium.arc.home.HomeActivity#0
03-05 13:39:32.560  5722  5722 W allstars.globa: JIT profile information will not be recorded: profile file does not exits.
03-05 13:39:32.561  5722  5722 I chatty  : uid=10060(com.klab.lovelive.allstars.global) identical 22 lines
03-05 13:39:32.561  5722  5722 W allstars.globa: JIT profile information will not be recorded: profile file does not exits.
03-05 13:39:32.669  5722  5722 I FirebaseInitProvider: FirebaseApp initialization successful
03-05 13:39:32.678   119  2041 D vndksupport: Loading /vendor/lib64/hw/gralloc.cros.so from current namespace instead of sphal namespace.
03-05 13:39:32.705   119  2041 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
03-05 13:39:32.705   119  2041 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
03-05 13:39:32.722   119  2041 E libEGL  : eglSetBlobCacheFuncsANDROID resulted in an error: 0x300c
03-05 13:39:32.722   119  2041 I OpenGLRenderer: Initialized EGL, version 1.4
03-05 13:39:32.722   119  2041 D OpenGLRenderer: Swap behavior 2
03-05 13:39:32.731   119  2041 E OpenGLRenderer: Device claims wide gamut support, cannot find matching config, error = EGL_SUCCESS
03-05 13:39:33.044   597   597 D ArcAppTaskTracker: Calculating task stack diff.
03-05 13:39:33.046   597   597 D ArcAppTaskTracker: Task created: 19 - ComponentInfo{com.klab.lovelive.allstars.global/com.klab.lovelive.allstars.global.GlobalUnsafeMainActivity} .
03-05 13:39:33.084   597   597 D ArcAppTaskTracker: Active task: 19.
03-05 13:39:33.326   119   145 I system_server: NativeAlloc concurrent copying GC freed 59995(3MB) AllocSpace objects, 41(1780KB) LOS objects, 42% free, 9MB/16MB, paused 9.666ms total 596.473ms
03-05 13:39:33.339   119   141 W System  : A resource failed to call release.
03-05 13:39:33.353   119   141 W System  : A resource failed to call release.
03-05 13:39:33.433  5722  5741 I FA      : App measurement is starting up, version: 16250
03-05 13:39:33.433  5722  5741 I FA      : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
03-05 13:39:33.433  5722  5741 I FA      : To enable faster debug mode event logging run:
03-05 13:39:33.433  5722  5741 I FA      :   adb shell setprop debug.firebase.analytics.app com.klab.lovelive.allstars.global
03-05 13:39:33.491  5722  5722 D OpenGLRenderer: Skia GL Pipeline
03-05 13:39:33.561  5722  5722 D JackpotPlatformMessage: ActivityCallback.onCreate(Bundle)
03-05 13:39:33.586  5722  5722 D ArcInputCompatHandler: Using touchscreen emulation for all games.
03-05 13:39:33.586  5722  5722 D ArcInputCompatHandler: Using touchscreen emulation for unity apps.
03-05 13:39:33.612  5722  5732 I allstars.globa: Background concurrent copying GC freed 9369(1199KB) AllocSpace objects, 8(224KB) LOS objects, 50% free, 1757KB/3MB, paused 5.478ms total 81.917ms
03-05 13:39:33.641  5722  5722 D vndksupport: Loading /vendor/lib64/hw/android.hardware.graphics.mapper@2.0-impl.so from current namespace instead of sphal namespace.
03-05 13:39:33.641  5722  5722 D vndksupport: Loading /vendor/lib64/hw/gralloc.cros.so from current namespace instead of sphal namespace.
03-05 13:39:33.709   119   297 I ActivityManager: Displayed com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity: +1s291ms
03-05 13:39:33.710   119   287 W system_server: Failed to determine oat file name for dex location /data/app/com.klab.lovelive.allstars.global-gx42EdHfqpRKf5asfmQ7aw==/base.apk: Dalvik cache directory does not exist
03-05 13:39:33.715   119   403 D ActivityManagerInjectorArc: taskOcclusionChanged: taskId=19 does not support PIP
03-05 13:39:33.900    11    47 W SurfaceFlinger: Attempting to set client state on removed layer: Splash Screen com.klab.lovelive.allstars.global#0
03-05 13:39:33.900    11    47 W SurfaceFlinger: Attempting to destroy on removed layer: Splash Screen com.klab.lovelive.allstars.global#0
03-05 13:39:34.072  5722  5747 I Unity   : SystemInfo CPU = ARM64 FP ASIMD AES VMH, Cores = 2, Memory = 3806mb
03-05 13:39:34.072  5722  5747 I Unity   : SystemInfo ARM big.LITTLE configuration: 2 big (mask: 0x3), 0 little (mask: 0x0)
03-05 13:39:34.076  5722  5747 I Unity   : ApplicationInfo com.klab.lovelive.allstars.global version 1.0.1 build 242cadff-95df-41d3-9bc5-9ab51555b9b0
03-05 13:39:34.076  5722  5747 I Unity   : Built from '2018.4/staging' branch, Version '2018.4.2f1 (d6fb3630ea75)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
03-05 13:39:34.167  5722  5741 I FA      : Tag Manager is not found and thus will not be used
03-05 13:39:37.838   119   358 W InputDispatcher: channel 'a1a6cc com.klab.lovelive.allstars.global/com.klab.lovelive.allstars.global.GlobalUnsafeMainActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
03-05 13:39:37.838   119   358 E InputDispatcher: channel 'a1a6cc com.klab.lovelive.allstars.global/com.klab.lovelive.allstars.global.GlobalUnsafeMainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
03-05 13:39:37.839    43    43 I Zygote  : Process 5722 exited cleanly (0)
03-05 13:39:37.840   119   403 I WindowManager: WIN DEATH: Window{a1a6cc u0 com.klab.lovelive.allstars.global/com.klab.lovelive.allstars.global.GlobalUnsafeMainActivity}
03-05 13:39:37.840   119   403 W InputDispatcher: Attempted to unregister already unregistered input channel 'a1a6cc com.klab.lovelive.allstars.global/com.klab.lovelive.allstars.global.GlobalUnsafeMainActivity (server)'`

This is where the application dies
`03-05 13:39:37.840   119   532 I ActivityManager: Process com.klab.lovelive.allstars.global (pid 5722) has died: fore TOP
03-05 13:39:37.842   119   532 W ActivityManager: Force removing ActivityRecord{df7a9b3 u0 com.klab.lovelive.allstars.global/.GlobalUnsafeMainActivity t19}: app died, no saved state
03-05 13:39:37.843   119   291 W libprocessgroup: kill(-5722, 9) failed: No such process
03-05 13:39:37.843   119   291 I libprocessgroup: Successfully killed process cgroup uid 10060 pid 5722 in 2ms
03-05 13:39:37.846   119   532 E ActivityManagerInjectorArc: taskDragFinished: taskId=19 has invalid operation
03-05 13:39:37.856   119   297 W ActivityManager: setHasOverlayUi called on unknown pid: 5722
03-05 13:39:37.903   119   358 I InputDispatcher: Dropping event because there is no touchable window at (896, 479).
03-05 13:39:37.966   119   365 E ArcGfxMetrics: Failed to find pattern in output: Janky frames: (\d+) \(.+\%\).
03-05 13:39:37.968   885   898 D ArcMediaControllerManager: onTaskMovedToFront: 2
03-05 13:39:38.058   597   597 D ArcAppTaskTracker: Calculating task stack diff.
03-05 13:39:38.058   597   597 D ArcAppTaskTracker: Task destroyed: 19 .
03-05 13:39:38.059   597   597 D ArcAppTaskTracker: Active task: 2.
03-05 13:39:38.078   885   898 I ArcMediaControllerManager: onAppBecameActive: org.chromium.arc.applauncher
03-05 13:39:38.195   597   597 D ArcAppTaskTracker: Calculating task stack diff.
03-05 13:39:38.196   597   597 D ArcAppTaskTracker: Active task: 2.

Is there a way to view a more detailed log about the application because the log doesnt seem to say WHY the application died, it just says that the application died.

Does the app work on a regular Android device and an emulator?

@Robert , yes, the application works in emulators like bluestacks and on regular android devices.

I rooted the android partition on my chromebook (Didnt install supersu tho) and now older versions of the application will launch (The newest version doesnt support root) What should I do next?


text:
My Android phone does not start - how to isolate hardware issue?
I use Moto G6 ALI with a custom ROM Pixel Experience running Android 11. So far so good and I was using this setup for almost two weeks as my daily use phone.
Today suddenly the phone froze when opening Whatsapp. No further response on the screen was observed. I had to restart the phone by pressing the power button for more than 5 seconds. Since I have unlocked by bootloader several years ago, I saw the boot locker unlocked warning. This usually stays for 5 seconds and then after I usually the boot animation.  But this time there is no movement beyond the unlock warning.
I had flashed TWRP recovery and tried booting with it by pressing Vol-Down+Power button and then choosing "Recovery".  The phone started the recovery mode but stuck with TWRP logo.
I then restarted to bootloader and gave the command "fastboot devices" and my device was recognised. So I downloaded the 64bit version of the recovery image and temporarily booted with the command "fastboot boot mali.img".  This too stuck at the same point.  Any clues on how to go ahead?

thanks, @alecxs, I am not worried about the user data as I have a back up of all app data and all that I am worried about is to make use of the phone. An Interim update: Ran fastboot erase cache
fastboot erase userdata - boot loop and running some script in recovery - TWRP
fastboot boot 1\malix64.img - boot loop again. Yet to check further.

Thanks @alexcs the two format commands restored the device; I was able to boot into PE11 well. Of course my apps and files and data are lost, but I am not worried as I can restore them. I have my device useful again. Can you please remove these comments and post as an answer so that I can accept it as a solution?

To be precise, I had further issues in booting to PE11. All wiping through TWRP did not succeed. Since I have PE11 install ZIP in my SDCard, I initiated the installation which went smoothly and I have a fresh working device now. Thanks again.

If your device received update recently which was already scheduled waiting on reboot, the instruction is placed in /cache/recovery/command TWRP may stuck on that instruction. this can be cleared by formatting cache partition
TWRP Commandline Guide
If device stuck on TWRP splash screen you still might have command line access via adb. Note daemon has 30 second delay on start, adbd is not ready when TWRP is boot-looping
adb shell format cache

or manually if partition is not in fstab
adb shell
find /dev/block -name by-name
mke2fs /dev/block/bootdevice/by-name/cache

If bootloader is unlocked you can also format from fastboot
fastboot format:ext4 cache

For further analyzing boot-loop usb-debugging is required. On unlocked device you can enable by modifying default.prop

download ROM according to your version
unpack boot.img and extract with AIK
modify ramdisk/default.prop and repack
flash image-new.img into boot partition

(you can read how it works here)
Why "adb root" does nothing?
  ro.adb.secure=0
  ro.secure=0
  ro.debuggable=1
  persist.service.adb.enable=1
  persist.service.debuggable=1
  persist.sys.usb.config=mtp,adb

If your device is booting far enough you should be able to capture some log during boot. For details and more information on debugging refer to the logcat wiki
Reading and Writing Logs


text:
F2FS partition does not mount, fsck.f2fs does not resolve. I want to recover the files
I made a backup of my phone's userdata partition with the command (because the /data is not mounting):
dd if=/dev/block/bootdevice/by-name/userdata of=/usb_otg/userdata.img
I need the files that are on the userdata partition. If anyone know a method of recovery that is also accepted.
INFO

Whatever I type, be it number, letter, or symbol, it accepts and shows it.

/data partition doesn’t mount.

I already used fsck.f2fs but it doesn't solve.

I found this in recovery.log:

E: Bad Magic for real block device
Could not mount /data and unable to find crypto footer

tw_includ_crypto=true

crypto ready=1

ro.crypto.type=file

ro.crypto.state=encrypted

Fsck.f2fs log
I:operation_start: 'Repair Partition'
Repairing Data using fsck.f2fs...
I:Repair command: /sbin/fsck.f2fs /dev/block/mmcblk0p42
        Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 25009920 (12211 MB)
Info: MKFS version
  "Linux version 3.10.49-gd8d6af5 (hudsoncm@ilclbld35) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Nov 3 03:35:22 CDT 2017"
Info: FSCK version
  from "3.10.108-Lynx-v2.5+ #1 SMP PREEMPT Sun Dec 20 11:16:12 IST 2020"
    to "3.10.108-NPD26.48-24-1-g285c0940a98 #1 SMP PREEMPT Mon Oct 19 14:51:51 UTC 2020"
Info: superblock features = 1 :  encrypt
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 25009920 (12211 MB)
Info: CKPT version = 7b4b2
Info: Found valid nat_bits in checkpoint
Info: checkpoint state = 281 :  allow_nocrc nat_bits unmount
[ASSERT] (sanity_check_nid: 372)  --> nid[0x3] ino is 0

[FSCK] Unreachable nat entries                        [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking                [Ok..]
[FSCK] Hard link checking for regular file            [Ok..] [0x0]
[FSCK] valid_block_count matching with CP             [Ok..] [0x0]
[FSCK] valid_node_count matcing with CP (de lookup)   [Ok..] [0x0]
[FSCK] valid_node_count matcing with CP (nat lookup)  [Ok..] [0x0]
[FSCK] valid_inode_count matched with CP              [Ok..] [0x0]
[FSCK] free segment_count matched with CP             [Ok..] [0x17a6]
[FSCK] next block offset is free                      [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs                           [Fail]
Info: Write valid nat_bits in checkpoint

Done.
I:/sbin/fsck.f2fs /dev/block/mmcblk0p42 process ended with RC=0
Done.

Recovery.log
Starting TWRP 3.4.0-0-35475b1d on Sat Jan 10 18:51:21 1970
(pid 209)
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/msm_hsusb/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:LANG: en
Starting the UI...
setting DRM_FORMAT_RGB565 and GGL_PIXEL_FORMAT_RGB_565
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 1280)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 255
TW_SCREEN_BLANK_ON_BOOT := true
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 255
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.666667x, 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)
I:Blacklisting input device: hbtp_vm
=> Linking mtab
=> Processing /etc/twrp.fstab for SAR-detection
I:Reading /etc/twrp.fstab
I:Done processing fstab files
I:SAR-DETECT: SAR System detected
=> Processing /etc/twrp.fstab
I:Reading /etc/twrp.fstab
I:Processing '/system'
I:Created '/system_root' folder.
I:Processing '/system_image'
I:Processing '/data'
I:Processing '/cache'
I:Processing '/boot'
I:Processing '/recovery'
I:Processing '/persist'
I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 1970-01-10--18-51-21
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:Processing '/firmware'
I:Processing '/misc'
I:Processing '/external_sd'
I:Created '/external_sd' folder.
I:Processing '/usb_otg'
I:Created '/usb_otg' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
E:Bad magic for real block device /dev/block/bootdevice/by-name/metadata
Could not mount /data and unable to find crypto footer.
I:Setting up '/data' as data/media emulated storage.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
Failed to mount '/data' (No such file or directory)
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
Unable to recreate /data/media folder.
I:Backup folder set to '/data/media/TWRP/BACKUPS/0021404064'
I:Settings storage is '/data/media'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
Updating partition details...
Failed to mount '/data' (No such file or directory)
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'auto'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
Unable to mount storage
I:Unmounting main partitions...

Partition Logs:
/system_root | /dev/block/mmcblk0p41 | Size: 2283MB Used: 1087MB Free: 1195MB Backup Size: 1087MB
   Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p41
   Display_Name: System
   Storage_Name: System
   Backup_Path: /system_root
   Backup_Name: system
   Backup_Display_Name: System
   Storage_Path: /system_root
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files

/system_image | /dev/block/mmcblk0p41 | Size: 2320MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p41
   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

/data | /dev/block/mmcblk0p42 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
   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
   Symlink_Mount_Point: /sdcard
   Primary_Block_Device: /dev/block/mmcblk0p42
   Crypto_Key_Location: /dev/block/bootdevice/by-name/metadata
   Display_Name: Data
   Storage_Name: Internal Storage
   Backup_Path: /data
   Backup_Name: data
   Backup_Display_Name: Data
   Storage_Path: /data/media
   Current_File_System: f2fs
   Fstab_File_System: f2fs
   Backup_Method: files
   Mount_Flags: 3078, Mount_Options: discard,inline_xattr,inline_data
   MTP_Storage_ID: 65537

/cache | /dev/block/mmcblk0p40 | Size: 254MB Used: 70MB Free: 183MB Backup Size: 70MB
   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/mmcblk0p40
   Display_Name: Cache
   Storage_Name: Cache
   Backup_Path: /cache
   Backup_Name: cache
   Backup_Display_Name: Cache
   Storage_Path: /cache
   Current_File_System: f2fs
   Fstab_File_System: auto
   Backup_Method: files

/boot | /dev/block/mmcblk0p31 | Size: 16MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p31
   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/mmcblk0p32 | Size: 16MB
   Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
   Primary_Block_Device: /dev/block/mmcblk0p32
   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

/persist | /dev/block/mmcblk0p29 | Size: 3MB Used: 0MB Free: 3MB Backup Size: 0MB
   Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Mount_To_Decrypt
   Primary_Block_Device: /dev/block/mmcblk0p29
   Display_Name: persist
   Storage_Name: persist
   Backup_Path: /persist
   Backup_Name: persist
   Backup_Display_Name: persist
   Storage_Path: /persist
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files
   Mount_Flags: 1030, Mount_Options: barrier=1,noauto_da_alloc

/firmware | /dev/block/mmcblk0p1 | Size: 35MB Used: 31MB Free: 3MB Backup Size: 31MB
   Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Mount_To_Decrypt Mount_Read_Only
   Primary_Block_Device: /dev/block/mmcblk0p1
   Display_Name: firmware
   Storage_Name: firmware
   Backup_Path: /firmware
   Backup_Name: firmware
   Backup_Display_Name: firmware
   Storage_Path: /firmware
   Current_File_System: ext4
   Fstab_File_System: ext4
   Backup_Method: files
   Mount_Flags: 6, Mount_Options: barrier=0,context=u:object_r:fsg_file:s0

/misc | /dev/block/mmcblk0p9 | Size: 0MB
   Flags: IsPresent
   Primary_Block_Device: /dev/block/mmcblk0p9
   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 |  | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
   Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
   Primary_Block_Device: /dev/block/mmcblk1p1
   Alternate_Block_Device: /dev/block/mmcblk1
   Display_Name: MicroSD Card
   Storage_Name: MicroSD Card
   Backup_Path: /external_sd
   Backup_Name: external_sd
   Backup_Display_Name: MicroSD Card
   Storage_Path: /external_sd
   Current_File_System: auto
   Fstab_File_System: auto
   Backup_Method: files
   MTP_Storage_ID: 65538

/usb_otg |  | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
   Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
   Primary_Block_Device: /dev/block/sda1
   Alternate_Block_Device: /dev/block/sda
   Display_Name: USB-OTG
   Storage_Name: USB-OTG
   Backup_Path: /usb_otg
   Backup_Name: usb_otg
   Backup_Display_Name: USB-OTG
   Storage_Path: /usb_otg
   Current_File_System: auto
   Fstab_File_System: auto
   Backup_Method: files
   MTP_Storage_ID: 65539

I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
Failed to mount '/data' (No such file or directory)
I:Actual block device: '/dev/block/mmcblk0p42', current file system: 'f2fs'
I:Unable to mount /data/media during GUI startup.
I:Loading package: TWRP (/twres/ui.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/uk.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/tr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sv.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/sk.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/ru.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_PT.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pt_BR.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/pl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/nl.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/it.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/hu.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/fr.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/es.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/el.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/de.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/cz.xml' directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:PageManager::LoadFileToBuffer loading filename: '/twres/ui.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.666667x, 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

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

https://github.com/topjohnwu/Magisk/issues/3171#issuecomment-729814931

https://superuser.com/q/1225447


text:
Is it better to charge your battery above 50% or let it go down, technically speaking?
Following up on this question:
Is it better, when the battery is at 40% to let it drop (use the phone until it's 30% for example) or to let it charge to 70%?
As far as I understand 50% is the "ideal" situation, but is it better to be "overcharged" or "undercharged" (for maximum life of the battery)?

Most modern devices have circuitry and software controls in place to prevent over charging, over discharge, and over cycling (that's a thing too). This has been talked to death and unless you are doing things that cause it to overheat, normal use isn't going to be improved much by any technique that limits deep cycling. Those days are largely past us. That said, you can increase your batteries longevity by following some basic rules, but honestly in modern phones the gain is minimal. https://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

Things have improved a lot since this question was addressed 5 years go... Today these things are much less of an issue, even the batteryuniveristy article linked above is kind of outdated. Due to how phones charge today, slowing the charge as battery level increases, the detriment to the lifespan of the battery is greatly reduced by going outside of the 40-90 percent range because of better technology and better batteries. I don't know anyone who recommends anything except "don't let your battery go completely dead" if you can avoid it, and even then once in a while is OK


text:
Erase content of stolen phone, but thief has my PIN
My phone was stolen.
I tried to erase it but the only option was set up erase. The problem is I believe the person that has my phone also has my PIN which would give them access to the phone. I know the setup erase and erase are two different things but I'm not sure how they each function. I would like to erase the content so once they are in the phone there is nothing to see because I have a lot of sensitive information on it. If the information is revealed, it would be damaging. The phone is a TCL A2X.
Is this possible, or am I screwed?

https://www.google.com/android/devicemanager


text:
Is it possible to change the Android ID with root access? (On Android 10)
I have an Android 10 phone (Motorola Moto G9 Play) and I want to change the Android ID (I think that's what apps use to identify you sometimes).
I have a cell phone with: ROOT + Magisk + EdXposed
I always changed my "Android ID" using "Titanium Backup". But there is currently no option to change.
Is it possible to change the "Android ID" just using a few tools, command line, applications, something that can modify the "Android ID"?
Please, I need it so much.
Reason: Some applications when they are going to ban accounts, they block the "Android ID" and I need to modify it and then use it again!
(By Google Translator, sorry!) =(

Is it possible to change Android ID without root access nor factory reset?

Where is the “android_id” stored and when does it change?

Thank you very much for the 2 responses.

If I change an application's SSAID from "aaaabbbbcccc1111" to "aaaabbbbcccc2222" for example. After I update it, or reset the settings, does it lose "aaaabbbbcccc2222" and go back to the original SSAID "aaaabbbbcccc1111"?

What exactly happens if I delete the line with (name = "userkey")?

Your device already uses the app-specific persistent ANDROID_ID. I have not checked the AOSP source code how this is implemented but based on your experience I would assume that for each app that has been ever installed in some SQlite or XML file the generated ANDOIRD_ID is kept.


text:
How many hours long "continuous video" can you shoot on Huawei P30 Lite 2019 model?
I want to shoot an extremely long video (almost 6-8 hours). Is the Huawei P30 Lite 2019 model BLE able to do it?
If not, for how many hours will it last?

Storage (including max allowed file size) and battery are two major limiting factors. Tune your camera app settings to whatever you like (FPS, resolution etc.) and record a video of a few minutes. Then estimate how much storage and battery it consumes. No answer here can be more realistic than this estimation.

Will the device be plugged in to a power source, or rely on its battery?

Note that if you can keep the screen off while shooting the video, the device will use significantly less power.

Also be aware some camera apps restrict video size //File system of device also plays a role (you can't record more than 4GB on ExFAT) // I would suggest do a trial run for as long as you want to actually record to avoid surprises

@beeshyams Is there a reason why "you can't record more than 4GB on ExFAT"? FAT32 has a file size limit of 4GB but ExFAt's file size limit is 16 exbibytes.

@ReddyLutonadio sorry, it was a typo - I meant FAT32


text:
When performing an adb pull of an entire device, why do I see /proc/self/root in pathnames repetitively?
When performing adb pull / on a non-rooted device, I see hundreds of items with pathnames that begin with /proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root/proc/self/root?
That's not a typo.  That is literally how the path of each of these items is prefaced.
It looks recursive or like an infinite loop, but eventually the repetition ends with a unique file or folder name.
What is going on?  What is adb doing here?

Usually that happens when dealing with chroot and/or mount namespace. /proc/<pid>/root points to the rootfs a process is seeing. Doing adb pull on "entire device" doesn't make sense. You should at maximum pull only persistent storage partitions, not pseudo filesystems.

@IrfanLatif Yes, I'm undoubtedly trying to capture a gnat with too large of a net.  I was trying to apply some of the tips provided in https://android.stackexchange.com/questions/234446/on-a-non-rooted-device-can-adb-access-any-files-that-an-android-file-manager-ca, and so I cast the net as wide and large as possible.  I'm searching for anywhere the lost data could be stored (cache, temp files, etc.), and so I tried pulling everything starting at root to try to get everything possible.

User data is stored nowhere ever except on /data.

/ is just tmpfs in RAM and does not survive reboot. there is no benefit in pulling / no matter device is rooted or unrooted. it makes lot more sense to pull physical partitions, although only one partition is of any use

And also that won't succeed because some pseudo files (like /dev/zero and /dev/urandom) have no end of file. You'll get an infinitely increasing file.


text:
Effect of removing the -k part in the ADB command
I uninstalled two services using adb command without the -k switch, in particular I typed:
pm uninstall --user 0 com.android.bips
pm uninstall --user 0 com.android.printspooler
Is there a a proper command to restore them back? I tried: pm enable --user 0 & all it said "enabled" (as shown in screenshot), but I can't find them anywhere. I know that if I removed the user 0 switch then I'm out of luck but I kept this switch and just took the -k switch off to clean up any residual files with these services. Am I still out of luck?
one more question: Will factory resetting my device using the option found in Settings>System>advanced on my pixel 4a phone is enough to restore everything back to the state before applying ADB commands?
P.S. My device is non-rooted

Can you please edit your question and include the full command you have executed for uninstalling the services?

@Robert this seems the continuation of OP's previous question

@AndrewT. No matter if this is a continuation question, IMHO every question has to contain all relevant information. Therefore I asked the author to include all the relevant information. As he is not to stackexchange I thought some "critics" may be good for learning how to ask good questions.

@Maged Please do not use comments to add essential information instead edit your question. You can edit your question at any time if you want to add important information. A reader encountering your question should be able to understand it without having read all the comments.

@Robert Yeah very sorry for all the confusion. I edited the original post and added a screenshot of the exact feedback I got from ADB commands but I'm still confused why I can't find these services if I got "enabled"?!

@Maged Thanks, but for future posts please don't post screenshots of a terminal just showing text. You can simply copy the text and paste it into your question and format it as code, this way it can be processed by Internet search engines.

Sure I will. I'm not just not as geeky as you guys so I find it harder to select text from a terminal. Anyway, I just wanted to show everything as it is for your analysis.

Is my situation mysterious to figure out what is going on? At least, is it possible to have these two services shared with me via that app "APK extractor" or something similar to it from a Pixel 4a device (US version)?

@Maged try adb install-existing com.android.bips. You didn't really uninstall the app from the device (just made it invisible for the user), so it's still there.

it didn't work as it gave me: inaccessible or not found

from your screenshot i see you forgot 'cmd package' nevertheless the 'pm enable' looks successful. you maybe just don't see icons in app drawer even already enabled (btw in windows terminal you can mark text with mouse cursor and copy to clipboard with enter key)


text:
Viber picture not found
I bought a new device i transfer eveything through smart switch. I can't see my images in my viber chat (media links) only the last two images .I can see everything in my gallery not in my viber chat.

May be this is the answer
Overview:
To completely migrate Viber, you will have to copy your message databases from old device and set them to Viber's own on new device. In addition, if you want to have all photos and videos from your conversations, you must migrate them too.
How to:
You need both devices rooted
On both devices install some Root File Manager (further "RFM"), like Total Commander or ES File Explorer.
On the new device install Viber and activate your mobile number. You message board will be empty for now.
Lets backup your user photos and videos:
On old device go to directory, where Viber user data files installed. In most cases it will be your Home directory, such a /storage/sdcard or /mnt/sdcard or /storage/Emulated/0, etc. In most cases it is in your Internal memory, but if someone chose to move Viber to SD card, then he/she have to go to /storage/extsd or/mount/sdcard2 or whatever it named in his/shes particular system.
In this directory Viber directory will exist (with "media" directory inside, just for proper identification). Directory Viber contains all downloaded user photos and all images and videos from your conversations. As many videos you send and receive, as big it will be. You will need to backup this directory.
If you have external SD slot, use it for copying mentioned directory to SD card. If you do not have such, use any other method allowed by chosen RFM - send it by FTP to your PC/new device, send it by e-mail to yourself, share it to Google Drive etc.
Lets copy message databases from old to new device:
On the old device open RFM and go to /data/data/com.viber.voip/databases/. There you will find 6 files (in 3 corresponding pairs); you will need all of them, so copy them all to your external SD or so, as I mentioned before.
Well, we finished with old device. It's up to you now for not pollute our planet throwing it to the trash mindlessly and consumingly.
On new device go to the same directory and see the same files there. 3 of them (those without .journal extension) will have permissions rw-rw---- (or 660), and the rest 3 - rw------- (or 600). You may see permissions right after file name, or you must get file property - it depends on RFM. Remember those "permission map".
Choose any current file and get his Properties in chosen RFM. You will see UID/GID (Owner/User and Group ID) of it either in form of owner name (like Viber) or system name (like u0_a92) or user ID (like 1092). Remember this UID or write it down.
Now you can copy all 6 "old" files from SD (or whatever else place you copy them before) to current location (/data/data/com.viber.voip/databases/) on new device.
Lets set proper rights to message databases:
Some of RFM (as Total Commander) allows to do group operations with permissions and UID/GID. Select all 6 files and get Properties of them. If your RFM allows you to set now Owner/Group or permissions, you lucky man; if not, you will must do next steps repeatedly for each single file.
Now you will need correct UID you remembered/written down before. If you thought you should easy remember u0_a92, but you don't, and now you are in doubts about correct UID, don't panic. Parent directory (/data/data/com.viber.voip/databases/) have the same correct UID, so cancel, go one level up and get it in it Properties.
For all 6 files in /data/data/com.viber.voip/databases directory get it properties and there set correct UID, which you remembered before (instead of current "root", set during copy by RFM). Probably you will be pushed by RFM to choose from a (long) list of existing UIDs, instead of writing down user ID manually.
For the same 6 files set the same correct GID as in previous step.
In file properties (for each fileset of 3 files) set correct permissions, as you remembered before (according to "permission map").
Lets restore your photos and videos:
Go to the Viber installation directory on the new device (usually /storage/sdcard if there is internal memory) and copy there Viber directory, you backed up in Step 4.
Go to Settings -> Applications -> Viber and Force Stop it.
Start Viber and enjoy your migrated conversations, with photos and videos, as nothing never happens.
P.S. I really do not understand why Viber have no will to implement this easy procedure.

As it appears your solution worked, you should write your "How To" as an answer to your own question. Answering your own question is allowed on StackExchange sites.

I am not sure, I just found a possibe answer to my question, I wiil have to try it first


text:
How do I remove the change keyboard button in android 11?
I keep hitting it instead of the spacebar and I want to remove it from the keyboard if I can. Circled in the photo.

This looks like the standard GBoard keyboard. As Android allows you to install other keyboard apps you can search for a keyboard that has a different layout.


text:
Is there a way to record myself while I use an application other than the camera?
I would like to record myself playing music. At first, I could easily open the Android Camera app and record. However, I need that the PDF document containing the sheet music be open on my smartphone so that I can see what notes to play.
If I open the Android Camera app, start recording and go to another app, the Camera will cancel the record.

That seems to be a limitation of your camera app. Google Play Store contains other camera apps that claim to be able to record videos while in background. https://play.google.com/store/search?q=video%20record%20background&c=apps

In this particular case you are much likely to benefit from taking a print out and use that instead of following a PDF.


text:
How to export contacts from the command line in standard format?
If a phone gets itself into a bad state and starts rebooting for no good reason, is there a way to export the contacts info so that after the phone is restored, the contacts can be reinstated? I don't think they were stored to the SIM.

Do you use Google Play Store on your phone? If yes you are logged in with Google and contacts should be synced to Google Contacts. Check it out: https://contacts.google.com SIM contacts are nowadays used only by a few people, mainly because each entry only supports one name + one phone number.

No, I don't. The phone is in a boot loop so I can only log in via adb.

On modern devices adb backup does not include contacts, see this question. Therefore only if your device is rooted you may be able to extract the contacts.

It would not be easy to export in standard format (do you mean a vcard/vcf?). You would want to try this answer first to verify whether adb can indeed access your contacts data or not. https://stackoverflow.com/a/59107487

Here is a shell script I use sometimes to export contacts from contacts2.db to VCF using sqlite3 commandline tool: https://android.stackexchange.com/a/215426/218526


text:
Frame stutters appear just when touching/swiping the screen on Android EMUI 8
I have heard about intensive apps causing frame stutters on Android, but this isn't apparently. I'm using a Huawei P10 Lite with Android EMUI 8 (Oreo), and the stutters in this case only happen when I touch/swipe on the screen. For example, if I swipe fast and then release my finger, the screen momentum effect on android just works fine, as it is 60fps, but when I physically touch the screen, doesn't matter the number of fingers I have on it, it just stutters, like if the framerate dropped to about 20 or 30 fps idk. However, I tried installing one of those control center dropdown menus for android, specifically the "Mi Control Center: Notifications and Quick Actions" by Treydev Inc; I did it because the dropdown menu was the first thing where I noticed the issue. It didn't work, and it seemed to drain my battery a bit, so I just removed it, and weird enough so did the stutter issue. For a while it seemed to be gone, and I tried rebooting the phone to make it sure, but after booting it back, the problem returned. I don't think it's any of the apps I have installed, as I only use duolingo, termux, duckduckgo and like. The phone isn't rooted, and no launchers or 'customization' apps are being used. If it's a video, android scroll momentum or anything, it just works fine, only when the screen is touched. Thanks in advance.

Also I have a P10 lite in the same configuration. I did not experience your problem, instead I experienced another one: the screen in a miniaturized form goes into a corner and is locked. It happens rarely and a screen turn off/turn on solves it.

Ok, this is quite an old one. I just did factory reset , partially due to the amount of junk files I had, and It worked back again. I still don't know what it is, but if anyone has a solution for those who have the same problem and don't wanna start again, I'll leave this post open to answers.

Did a factory reset fix the issue?

Yes, I did (for other reasons too), but as I say, there will be people that wouldn't want to do so just for that, so I am still looking from time to time for an answer. I marked it as solved cause technically it's solved, but I am looking for a better answer. Feel free to post one if you or someone has it!


text:
Android Chrome Password Pop-up
Does anyone know how to eliminate this annoying pop-up (see screenshot) in Chrome that has a separate window for passwords? I know it can be done but I can't find it and any every time I search for it, the result is only how to resolve the check your passwords compromised passwords pop up from chrome. Thanks in advance.

It is Chrome's password manager... If you don't want it, disable it. https://support.google.com/chrome/answer/95606

I don't want to disable the password feature, I just don't want the pop-up. An older version of Chrome had the fields just filled in rather than as a separate pop up. It's just another annoying "fix" and there's a way to disable it and go back to the old way but I just haven't found it. I had fixed it on a previous phone and cannot find the way to fix it again.

Chrome constantly changes.  This was one of the recent changes to Chrome.  The only way to disable the popup would be to delete the saved password for that particular website


text:
How can I enforce Google SafeSearch on Firefox/Chrome?
I'd like to enforce Google SafeSearch on Firefox/Chrome on Android.
Is there any way to do it? For example, if I enable it and then switch to Incognito/Private mode the setting will disappear.
For desktop, there are extensions which enforce safesearch for google. I'd like to have the same behavior on Android.


text:
Galaxy tab charging dock stops charging when USB device is attached
I recently bought this charging dock by Brodit for my Samsung Galaxy Active 2 (v. 3.9.0) with Android 9: https://www.amazon.de/gp/product/B00UASMT2Y/. I was hoping to constantly keep the tablet running at a fixed place.
If I put the tablet in the Charging dock, it starts charging as it should. If I now connect an OTG USB device (namely a SkyController 2 for a Parrot Drone), the dock seemingly stops charging. A measurement of the current between dock and tablet seems to confirm that.
The charging symbol in the tablet still stays on since the SkyController delivers the usual 0.5A. Of course, this is not enough to compensate for the energy lost, so the tablet's charge slowly decreases.
Is it really usual behaviour that connecting a USB device disables charging through the dock and, if yes, is there a switch in Android to change this?
If this is really not possible, is there another solution to keep the tablet charged while using a USB device at the same time?
Thanks in advance

In USB OTG mode the phone/tablet does not only stop charging, OTG is designed to deliver power from the phone/tablet to the attached OTG device. At least with micro USB I think it was standardized this way. But some devices may work differently. Charging and using an USB port at the same time was first standardized as far as I know in USB-C with power delivery.


text:
Copy private key from OpenKeyChain to tails GPG?
I have a private PGP key on OpenKeyChain that I'd like to move to tails.
There only seems to be one way to export from OpenKeyChain - choose to make the encrypted backup file? But I can't get the process to work.

I made a backup from Android, "backup.sec.pgp" (Noting the passphrase of hyphenated numbers)
Transferred it to tails
Ran 'gpg --decrypt backup.sec.pgp | gpg --import backup.sec.pgp'

It returns:
gpg: unknown armor header: Passphrase-Format: numeric9x4
gpg: unknown armor header: Passphrase-Begin: 96
gpg: AES256 encrypted data
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

Then I enter in the long hyphenated numerical passphrase and it spits out:
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key

Advice would be hugely appreciated

Just a typo, I got confused as well.
The right command is:
gpg --decrypt backup_YYYY-MM-DD.pgp | gpg --import

you typed the file name twice.
Hope it helps.

this may sound "extra" but. I believe it will get the job done. try using this method on pc or a Mac with this
https://www.openkeychain.org/faq/#how-to-import-an-openkeychain-backup-with-gpg
then make a backup and move it to tails.
if You've found a better way I'm all ears as I currently have to go through this pain in the ass. such a pain but both, wonderful services.
gl


text:
Oneplus 8T stuck in bootloop after flashing patched boot.img
I'm a complete newbie following a guide to root my phone, but it got stuck in a bootloop after rebooting, after flashing a patched boot.img created by Magisk. I have tried many things but with my lack of experience I'm stuck. One guide I'm following for unbricking your phone requires flashing all files from a stock (official) payload.bin file, but I can't run the commands because of a 'critical partition' error.
Running 'fastboot flashing unlock_critical' only prints out the syntax commands as if I just typed in 'fastboot' as is... I'm stuck, I'm clueless and I'm beginning to panic ._.

for patching, stock boot.img is required. furthermore unlocked bootloader is required for flashing magisk_patched.img from fastboot. because of this two requirements i see no constraint to unbrick your device by just reverting your modification. only flash stock boot.img


text:
Suspicious link on android
I accidentaly clicked on http://127.0.0.1:5555 this link on my android phone what should i do? i don't know anything about coding so please write with simple words to me

127.0.0.1 is the address of your phone itself. Therefore everything that can be loaded have to be generated by an app or an system service of Android on your phone. If there is no app listening on port 5555 then nothing will happen, the web browser will simply show an error page.
Therefore you don't have to worry.

127.0.0.1 is a loopback device... Meaning it is going back to itself (your own phone, 127.0.0.1 is your own device's internal address). Port 5555 is used by VPN's for transmitting and receiving encrypted traffic, so basically you clicked a link that redirected your request back to itself, or in other words it did nothing. You should be safe, malware is much less common than people want you to believe.


text:
Android phone as 4G proxy server
I am trying to turn my old phone (Xiaomi Mi 5) into a 4G proxy server which I can use with different apps for scraping data, etc. I have been searching on how to set it up and I found some articles, but they are not very clear. I am really a newbie and I have no idea how to set it up. I have bought 2 Android apps: Proxy Server Pro and Servers Ultimate Pro having trouble configuring it.
These are the steps I have followed on Servers Ultimate Pro:

Add a proxy server

In the General tab, I didn't touch anything
In the Rules tab, added a new rule

HOST CONTAINS: I put my public IP address which I found at https://myip.com
REPLY WITH THIS IP: 127.0.0.1 Port: 1080

Now, when I try to test it I, get no connection.

You can run tinyproxy from commandline. See my answer to using your android phone as a proxy server

unfortunately nope i have already checked that question. Basically it explains how to setup a proxy server via wifi, but i need it with mobile data. The thing is that when i use another app called Allproxy which is a fremium app it works it gives me the protocol://user:pass@host:port and it works it means that the ports from my ISP are opened and not blocked. But this app steals your data so i have heard and i don´t want to risk. I want to set it up myself via Servers Ultimate pro or Proxy Server pro. About your answer in that post i checked it but i am unable to code at all.

I still don't see the point in running a proxy on a mobile network only device. Are there any sites or resources that are only accessible from within the network of your cellphone provider?

@Robert because i manage social media and buying a mobile proxy costs way too much than turning my old device with a basic data plan into a proxy..

@MarianPepa I have never had a carrier plan which provides a public IP address, but I've been using a VPN VPS to get a static public IP when using mobile data. And tinyproxy always worked perfectly. It's free, open-source and very lightweight. Do consider it if you want a long term solution. Setting it up isn't difficult if you get basic familiarity with *NIX shell usage.

@IrfanLatif In Germany T-Mobile AFAIK has some older business plans with public IP. Also data plans dedicated for IoT may have a public IP, of course only by large old corporations which get their (large) IP range early in the Internet history so that they now still have enough IPv4 addresses.

but really it shouldn’t be so complicated after all. I am missing something i know it. I am a total newbie, can i post some screenshots to show you guys how did i configure it ?

@IrfanLatif i am definitely going to give it a try but in this case i would need a vps right? (which would be another extra monthly cost for me)

You don't need VPS if you have already a public IP. If you don't have, you cannot access the proxy server from internet whatever tool or app you use on Android to run the proxy.

@IrfanLatif my public ips are constantly rotating and previously with the apps i mentioned above i have been trying to set up also a Dynamic DNS updater (no-ip) how do i set this up with tinyproxy in my phone?


text:
Is it possible to record uncompressed or > 150000 kb/S video on a smartphone or tablet?
Is it possible to record uncompressed or > 150000 kb/S video on a smartphone or tablet?
If so, how and what devices are compatible? I am able to do this with cheap logitech webcams, however the best I was able to get with multiple smartphones/tablets was with a Moto G, which recorded compressed (mp4) video at 50000 Kb/S using UHD.
Intuitively, I expected to get higher quality video from smartphones and tablets. Am I missing something?


text:
How do you search for specific apps installed on Android?
How do you search for specific apps from installed apps on Android and the list them out? I need to search all apps installed on the device to check if three specific apps are among them. If yes, then I need to list all/any found installed.

You can use free and open source  AM Pre-release app. You can search for any installed app by its name and package name. You can sort apps by label, package name, user apps, system apps, disabled, last update, etc. At first run the app would ask you to setup adb or grant root access. Simply deny it or skip the step. It is optional.

Alternatively, you can also use another free and open source Permissions Manager X app developed by a fellow member of our community, Irfan Latif. The app offers search by name, package name, permissions. You can also exclude apps based on user/system app type and type of permissions.


text:
Nexus 7 2013 - stuck at android is starting optimizing apps. trying adb to get the data
I have a 2013 model Nexus 7.
It is running 6.0.1, unmodified with locked bootloader. USB debugging is on.
Battery drained to 0. Charged then the device is stuck on boot loop .. android is optimizing app X of x.
I don't wanna lose the data so I've avoided hard reset.

I've wiped cache more than once.

I tried ADB Commands .. and while on the android is starting I can list the device and I can list the directoies ..

Tried adb pull /
and it return this message.

c:\Adb>adb pull /

daemon not running; starting now at tcp:5037
daemon started successfully adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15:
Protocol not available

Tried shell to see if I can list folders and
Adb shell ls /sdcard/sdcard
it returns the same message.

c:\Adb>adb shell ls /mnt

asec

expand

media_rw

obb

runtime

sdcard *******************

secure

user

c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory

Is there any way that I can retrieve the data before hard resetting .. through adb or custom recovery .. or whatever.

@alecxs
The first command returns this >>
adb: error: remote object '/storage/emulated/0' does not exist

@alecxs
Second command returns this when trying to access the expand folder >> opendir failed, Permission denied

'adb shell "find /mnt /storage 2> /dev/null" > index.txt' will give you list of available files you can pull

@alecxs I successfully pushed a file .. c:\Adb>adb push H.txt /data/local/tmp H.txt: 1 file pushed, 0 skipped. 0.0 MB/s (13 bytes in 0.000s)

it might be /sdcard is protected with screen lock. try to gather some info from logcat maybe you figure out reason. if some app causes this you should be able to disable that app from package manager (pm). worth mention on factory reset you will lose MicroSD Card content too. maybe nvflash is of any help

I couldn't get the second command to give me a text file .. but running the command without the index.txt part. returns this. /mnt
/mnt/sdcard
/mnt/runtime
/mnt/expand

try again with 'find -L /mnt /storage 2> /dev/null' if still no result guess your files aren't accessable until screen will unlocked. therefore logcat is the way to figure out/fix

https://forum.xda-developers.com/showthread.php?t=3484879 try dirty cow exploit to get root shell. also this root method claims it is working from stock revovery without data loss (no mention of bootloader state) https://forum.xda-developers.com/showthread.php?t=3219148

Let us continue this discussion in chat.


text:
How to fix my micro SD card that became a read-only memory card?
Since the Android external memory card has turned to read only (also known as SD card write-protected) all of a sudden, I can no longer add, write, or delete things from it.
How to fix the SD card that mounted as read only?
Is there an application to solve this problem?

copy files to another MicroSD Card. in case of adoptable-storage use gddrescue for 1:1 clone


text:
How can I relock my Xiaomi bootloader without bricking the phone?
I unlocked the bootloader on my Xiaomi Mi A1, and it boots fine.
However, after I relocked it (using the top answer here) and rebooted, the phone flashed the white Android loading screen then went black. The same thing happens when I try to boot into recovery mode. I can still get into fastboot, though, and am able to unlock again.
How can I lock the bootloader and return to the stock Android that the phone was shipped with? I'm not worried about data loss.

https://xiaomifirmwareupdater.com/archive/miui/tissot

@alecxs Thanks, reinstalling Android via your link allowed me to lock the bootloader.


text:
Is it possible to control and transmit electromagnetic radiation of allowed frequency with Android device?
I understand the following things about smartphones

A smartphone has various hardware that functions wirelessly by transmitting and receiving electromagnetic waves.
Things like Wifi, Bluetooth, and phone calling all work by transmitting and receiving electromagnetic waves.
The frequencies that this hardware can emit are fixed. It cannot work in all frequencies. It can work in only part of the frequency spectrum.

Let us take the following example.
I want to use a smartphone to emit an electromagnetic wave of a particular frequency, say X Hz.
If this particular frequency is supported by the hardware, is it possible to control/emit this signal of this particular frequency, like using any apps?

Welcome to Android Enthusiasts! Take note that questions directly asking for app recommendations are off-topic. Instead, we prefer the asker to just state the underlying problem that they want to solve and not putting any restriction for apps-only. Otherwise, you might be interested in our sister site, Software Recommendations Stack Exchange instead.

A Wifi or Bluetooth devices works in 2.4GHz band but each chip is limited to Wifi or Bluetooth specific signals. Only a SDR (Software Defined Radio) can emit signals defined by software. If you want to generate frequencies defined by software I would recommend to look into decent SDR hardware boards. An Android device is as far as I know not good as SDR hardware.


text:
What is the application PlayAutoInstalls
I just updated my device (Xiaomi Mi Lite 10) and found an app with a name that concerned me.
The app name is "PlayAutoInstalls", seems a system app that I never used or installed, but I can't find information about it.

I never install anything outside Play Store, but this is not a guarantee of safety (malware) and I have the feeling that this one is a malicious app.
Any information about it's functionality (name is concerning), and if it's safe to remove?

App require no permission, except the ability to show notification.Is not clear to me how to show the package without installing anything

You would want to read this. https://www.programmersought.com/article/50995132696/ (follow from 2. heading). Also see https://www.reddit.com/r/Xiaomi/comments/764hir/what_is_this_pai_app_in_a1_that_cannot_be/

App names are nothing but text. More important is the app package name and it's signature. If you are curious about the app get it's APK file and upload it to virustotal.com - eg. using this app: https://play.google.com/store/apps/details?id=com.funnycat.virustotal

Possibly related: Become an Android Partner: "Automatically push predetermined apps and other customization features to phones during setup without creating multiple carrier builds for the same device."

Anyone who wants to investigate, APKMirror has the Apk. https://www.apkmirror.com/apk/xiaomi-inc/pai-2/


text:
How to root Redmi 4X?
I wish to install TWRP, LineageOS and Magisk on a Redmi 4X I have to replace the stock ROM.
I installed ArrowOS on a Lenovo Vibe K5 Plus very recently and it went very smoothly.
However searching around online, unlocking Redmi phones seem to be a real pain.
While this link tells how to root it and install TWRP(the easy part) it doesn't talk about the part of unlocking the phone's bootloader in the first place.
This link leads nowhere.
This link is pretty irrelevant because I don't have a Windows PC. Any tips to do this with Arch Linux??
I couldn't really make sense of this rather long and intimidating thread though it seems to be the most promising one.
I couldn't make any sense of the other google results and they lead me nowhere.
I'm still quite a noob with Android and so would appreciate any help I get.

VirtualBox platform package + Extension Pack // Windows ISO // miflash unlock tool

unlocking requires mi account and activated sim card bonded to device for 15 days. after this period unlocking works with miflash unlock tool. Francesco Tescari has reverse engineered miflash unlock and provides unofficial linux alternative MiUnlockTool.sh (requires java). There is also another linux build of unofficial XiaoMiTool V2 which provides bootloader unlocking

@alecxs, I installed xiaomitool-v2 (https://aur.archlinux.org/packages/xiaomitool-v2/)/ available in the arch user repository. But when I open it, it is apparently still in beta. So Will it be safe to use this tool? Can it make the phone COMPLETELY bricked?

Why do I need to keep an active sim in the phone? Can't it be done without the sim?

I just don't get how a VM running windows 10 can safely root a phone. Won't I get problems with drivers and such?

If it works in a VM, I'll do it in a VM, though I can't give more than 4 gb ram to the windows VM. I'll proceed in a VM if I can get any assurance about reliability from you since it is my mother's only phone and bricking it will be a complete nightmare.

Also should I download the 64-bit version of the Windows 10 ISO? Or is the 32 bit ISO sufficient? The only purpose I want it for is the unlocking of this device.

please consider deleting your comments if you think they are no longer relevant. you might include useful info/links in the answer below instead

So I successfully rooted my device and installed lineageos in it today.
I created an mi account(couple days back) witj my phone number, made a windows vm and used an [unofficial tool] [https://kkworld.in/unlock-mi-bootloader-without-waiting-time/] to unlock the bootloader.
Initially getting my vm to recognise connected usb devices was an issue but I found a [superuser solution][https://superuser.com/a/1295185] and then rebooting.
You can check if usb devices are working without turning on a vm. I've posted it [here][https://github.com/arch-linux-enthusiast/android-rooting/commit/3924a65d6681a4efd9fdfd2931b82d47321e3556]. Yep I've also made a github account (with very little substantial content since I barely know anything).
I didn't have any waiting time for the unlocking to happen, but keep in mind this tool is possibly modded as far as I know. If you have the patience, use the official tool and wait it out.
Thanks for all the support, I couldn't have done it without your help, @alecxs!!!