# Question
Title: APK signature verified but warns file "not protected by signature"?
I'm using apksigner to verify the authenticity of a Google Podcast apk that I downloaded from an apk mirror. This apk (and older versions) verifies successfully (v1/v2/v3) and returns exit code 0 but in the output I see this warning:

**WARNING: META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.**

I do not understand what the impact of that is. If the APK is signed, and verified, why do I see this warning? Does it mean the APK could be trojaned or modified? How could an attacker exploit that?

I am downloading some older versions of some Google apps and I want to be sure they aren't trojaned, which is why I'm trying to verify the authenticity before I install them on my phone.

# Answer
> 12 votes
### Summary

The warning you have encountered only applies to the APK signature v1, but as the APK file contains also a v2 and v3 signature you can safely ignore this message as every modification on the APK file can be detected by the newer signature schemes.

However even if the signature can be verified it does not mean that the APK file is genuine. It still could be resigned after modification, therefore you should carefully compare the certificate digests (shown when verifying it using `apksigner verify --verbose --print-certs`) of the APK to be verified and compare it to other APK files of the same app developer. See this answer of How can I verify the authenticity of an APK file I downloaded? for details how to compare the certificate digest of an APK.

### Detailed explanation

First of all as you can see what you get is a WARNING not an ERROR. If relevant file(s) of the APK file would have been modified the verification would fail and you would get an ERROR message.

To understand the warning message you need a little understanding of Java and how Java signatures (APK signature v1) work. This old signature is stored inside the JAR in two files: `META-INF/CERT.SF` and `META-INF/CERT.RSA`. Of course a signature can not sign the files it is written into , hence those files are excluded by the signature.

Additionally the META-INF directory is location of the `MANIFEST.MF` \- a file that is only relevant for Java on Desktop but not used by Android at all.

There can be additional files in the META-INF directory, considering the standard Java directory layout no code should be stored inside files within the META-INF directory.

Because of all this Sun as the original inventor of Java decided to exclude the META-INF directory from the Java code signature at all. Several years later Google just used the Java signature for APK files which is now known as APK signature v1.

Therefore for the APK signature v1 the files inside the META-INF directory are not covered by the signature and hence can be modified without being recognized if you only verify

Because of several attacks on the APK signature itself (such as including the same file multiple times with different content in the APK Google decided to develop a completely new APK signature that does not apply on the APK content but on the overall APK file itself. This was the beginning of APK signature v2 and it's successors.

These new APK signature schemes do sign the complete APK content at once, not excluding a single file that is stored inside the APK file.

Back to the Google Podcast APK, verifying it using apksigner outputs the following:

```
java -jar apksigner.jar verify --verbose "Google Podcasts Discover free trending podcasts_v1.0.0.301897054_apkpure.com.apk"
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
WARNING: META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader not protected by signature. Unauthorized modifications to this JAR entry will not be detected. Delete or move the entry outside of META-INF/.

```

As you can see the APK file is signed not only by an v1 signature but also a v2, v3 and v4 signature. This means that the WARNING only applies to the signature created by the v1 scheme. You can easily verify that by modifying a single character inside the file `META-INF/services/com.google.protobuf.GeneratedExtensionRegistryLoader` as it is stored uncompressed within the APK file. You can simple open the APK file in an hex editor, modify a character in the section that belongs to that file (it is the first ZIP entry within the APK) and then again verify the APK:

```
java -jar apksigner.jar verify --verbose "Google Podcasts Discover free trending podcasts_v1.0.0.301897054_apkpure.com - modified.apk"
DOES NOT VERIFY
ERROR: APK Signature Scheme v3 signer #1: APK integrity check failed. CHUNKED_SHA256 digest mismatch. Expected: <ac8a15569352655a22f13d3c565c2c0e5c62dc70c8f6f8c10f6fbfa63decb19b>, actual: <aa5622cd904500c38424562ef4b5be9e5716d10a85985a41f35e4ed834cee8fe>
ERROR: APK Signature Scheme v3 signer #1: APK integrity check failed. VERITY_CHUNKED_SHA256 digest mismatch. Expected: <56eeebd545733fd6408cd6a30b8bcf98a557076167902b6d9502b5aca86b78e89b42220000000000>, actual: <c37e1e1436cfd62f89592c48211ffb6ad2f1dff0f69d2203072f1e6c3872a5919b42220000000000>

```

As you can see now the APK signature is considered invalid. I don't know why the v3 signature fails first, may be the signatures are not verified in order v1, v2, v3... From my understanding all signatures except v1 should fail on the modified APK file.

---
Tags: security, apk, signature-error
---


# Question
Title: Determine what APPS are Android Auto Compatible
When I connect my cell phone to my vehicle, Android Auto displays a very limited list of APPs that are on my phone:

(The clipped APP at the bottom is weather).

Supposedly more APPs that are compatible with that interface will be released.

How do I determine if an APP on Google Play is compatible? I don't see anything on the Google Play webpage for a given APP that indicates it can be used or not used for Android Auto.

(In particular, I want navigation with offline maps beyond what Google Maps offers).

# Answer
There is a special category in Google Play Store that lists apps ready for Android Auto:

https://play.google.com/store/apps/collection/promotion\_3001303\_android\_auto\_all

If you have an APK and want to check if it is ready for Android Auto you can look at it's AndroidManifest.xml file inside the APK. It should contain an entry like this:

```
<meta-data android:name="com.google.android.gms.car.application" android:resource="...."/>

```

For more details see Add support for Android Auto to your media app.
> 3 votes

---
Tags: google-play-store, android-auto
---


# Question
Title: How do I translate an application that is protected and cannot be translated by AllTrans Xposed Module?
I've been trying to translate this application using AllTrans, yet I don't know how to do it by extracting and recompiling the APK?

# Answer
> 0 votes
Try Google Lens.. it can translate text directly from your screen. Pretty awesome.

Hope it helps

---
Tags: apk, localization, protected-apps
---


# Question
Title: How to clean app cache using script every time the phone boot?
I know there's many app that clean cache every boot but I would like to use init.d/script to save storage.

Dalvik-cache is /data/dalvik-cache/arm/ as I can just rm -rf *

But, app cache is located at /data/data/app\_name/cache and don't know how to automate it, because cache folder is a sub-directory

I'm new to bash scripting and this would help me significantly in programming overall

Phone is magisk'ed Android 10.

# Answer
> 1 votes
I forgot array is such a thing. I solved my own problem

```
# Assigning app-name into $apps
apps=($(ls /data/data/))

# Looping each app
for app in "${apps[@]}"; do

  # Deleting $app/cache/ contents
  rm -rf /data/data/$app/cache/*
  done

```

---
Tags: shell, android-10, cache, init.d
---


# Question
Title: Will joining notification be send to my contact number if he doesn't have it?
Suppose I have synchronised my contact but the person in my contact do not have my contact number, **will he receive my joining notification in telegram app?**

# Answer
No. He will only receive notifications of those people who are in his contact list.

Imagine a famous person getting 100s of notifications per day of people joining telegram he doesn't even know. LOL
> 0 votes

---
Tags: telegram
---


# Question
Title: Why are these picture-related apps blank?
I've been wondering a lot about this when it happened which I was using `Walli*` app yet after I have changed my ROM, maybe the app gets blank no matter how I install it. But after a time, I've also realized that there is another app called `Reface` with the same problem in which I can't use them because they're blank like there is no connection to the Internet.

Note: I'm using **Cloudflare Family DNS** on my router and Firewall settings such **SPI** and **DOS protection**. My ROM: `AOSP` based `7.1.`2 Android custom ROM

# Answer
The problem was solved by installing Exposed via recovery instead of Magisk
> 0 votes

---
Tags: applications, custom-roms, connection-issues, diagnostics
---


title: "Screen Recording" in LG Android

text:
# Question
Title: "Screen Recording" in LG Android
I have an LG V40, and in both Android 9 and 10, it seems that the "Screen Recording" app is always running, and not possible to keep it Stopped.

Greenify shows it as running in "Foreground":

If I force hibernation, seconds later it will be running in Foreground again.

It is not possible to disable this app, and it requires access to Camera and Microphone:

These permissions cannot be removed either:

Should I be concerned? Is there any way I can fully disable this app?

My OS is European.

# Answer
Use adb to disable the app. And download a trusted screen recorder.

**For installed apps:**
`adb shell pm list packages` should list all the packages on your device. Then use `adb shell pm disable <package_to_disable>` to disable an installed app.

**For system apps:**
For system apps just the disable command is different `adb shell pm disable-user --user 0 <package_to_disable>`

if you want to see the disabled apps use `adb shell pm list packages -d`

Take a look at this https://www.xda-developers.com/disable-system-app-bloatware-android/
> 1 votes

---
Tags: permissions, privacy, lg, disable-app, greenify
---


# Question
Title: Phone temperature sensor not working - Charging slow - How to fix?
Recently, something has happened to my phone's temperature sensor. It's showing ridiculously high values for the temperature (over 100 degrees), even though it's very cold. This has caused my phone to refuse fast charging, and it charges very, very slowly. (~7 hours to charge)

Is there anyway I could turn off a sensor or fake its value so that my phone charging returns to normal?

Or is there anyway to force the phone to ignore the thermal limits during charging? (I know it's dangerous but I have no choice)

Deleting the thermal engine file doesn't fix the issue.

P.S: Android 10 | Qualcomm chipset | Rooted + Xposed

# Answer
You have not mentioned anywhere that you have root access but since you've added aa root-access tag i'm assuming you have root access.

Sensor disabler is what you are searching for. Just be careful!

P.S.: Take a look at this too https://forum.xda-developers.com/moto-maxx/help/how-to-disable-temp-sensor-t3504585

Generally in all phones temperature is the battery temperature and as far as i have read in many threads this is rare and indicates terrible hardware issue. And there is no way to change the value. There must be a way to bypass the temperature check though. I'd recommend you to go to a shop and get it diagnosed.
> 0 votes

---
Tags: root-access, charging, sensors, edxposed
---


title: 3GB of internal storage is lost

text:
# Question
Title: 3GB of internal storage is lost
I have a Sony Xperia SL with 32 GB internal storage from which 25 GB is available for user. When I bought the phone, everything was OK. but last month I found out that there is only 1GB left free, when sum of the files in the memory was only 21GB. I deleted some files and reduced the filled capacity to 10GB. However, I still have only 12GB free on my device. It sounds like 3GB of my storage is lost. (I have checked LOST.DIR and, for those who want to know, I have considered the thumbnail files when I summed up the files)

# Answer
> 1 votes
Caching may be the problem. Cache and especially dalvik-cache sometimes can be really big. Cache can be deleted however dalvik-cache is can't be deleted if your phone is not rooted or you can uninstall some app anyway.

# Answer
> 0 votes
You should consider that applications can be space-intensive. Take the Facebook-application for instance. It consumed up to 2GB on my phone.

# Answer
> 0 votes
When things with storage go awry I use DiskUsage. It uses a graphical interface (hardware or software rendering), very intuitive. You can scan (look at) multiple areas. With this app you will be able to isolate (locate) the problem. After finding the space hog, you can delete within the app or use a file manager to perform more complicated tasks. Root will allow viewing system locations.

---

**I don't work/publish/design/develop/etc. on this app, nor do I receive any compensation for anything related to this app. It's just very useful**

**As always perform a backup before deleting anything**

# Answer
> 0 votes
Some times the dump files may eat up our storage space. Try using apps to clean up this space. I would recommend you sdmaid app which is free in play store. Its basically for rooted phone but works totally fine with unrooted ones too.

# Answer
> 0 votes
It might be some directories itself where the space ist lost. If you deleted a lot of files in a directory, the space is freed, but the space for directory entries is not reduced. You can help yourself with this (in a terminal):

```
mv dirname dirname.old
mkdir dirname
mv dirname.old/* dirname
rmdir dirname.old

```

This should give you back the lost space.

---
Tags: storage
---


# Question
Title: Package manager has died while checking permission
Caused by: java.lang.RuntimeException: Package manager has died at android.app.ApplicationPackageManager.checkPermission(ApplicationPackageManager.java:427)

Caused by: android.os.DeadObjectException at android.os.BinderProxy.transactNative(Native Method)

Can anyone help me what does this mean and how to prevent this?

# Answer
> 1 votes
A `DeadObjectException` can occur if two Android processes are communicating with each other and one of them dies while transferring data to the other. The other process will then throw a `DeadObjectException`.

In your case the "other" process was the PackageManager process which was communicating to a second process - may be a system service for listing packages?

There is not an easy solution how to prevent such an error. The only chance you have is by checking the `adb logcat` output for errors when you access the package manager.

The reason why the other process (whatever process it is) fails may be corrupt data.

---
Tags: applications, permissions
---


# Question
Title: How can I archive old contacts out of My Contacts?
On an Android (6.0), how can I archive old Google contacts where they do not show up in my contacts but they are listed in either:

* the google contacts website under *other contacts*
* archived in another app/cloud storage securely.

Ideally moving them from the archive to my contacts list would be doable from a mobile app, or the archive service would have a mobile website where they are accessible.

To clarify: I don't want to delete them forever or be inaccessible on mobile.

# Answer
Just with one account also you can achieve this.

1. In contacts app, go to menu and create a new label like "Archive"
2. Tap on label and add contacts.
3. From menu go to settings, and in "contacts to display" select customized, and expand your google account, now here all labels will be shown. Select all labels except Archive.

Now contacts moved to Archive label will not be shown in list.
> 4 votes

# Answer
**Tip:** Using a computer may make it easier to do this. However, you can also do it on a mobile browser.

1. In your mobile phone, make sure you have synced your contact list to Google Contacts.
2. Open **"Google Contacts"** at https://contacts.google.com/ preferably on a desktop or laptop.
3. Select any one contact by clicking the checkbox.
4. Open the **"Selection actions"** menu in the header toolbar and click **"All"**.
5. Go through your contact list and de-select the contacts you want to keep. The checkbox must be cleared for those contacts.
6. For the remaining contacts that are still checked, you are going to archive them. Click the *three dots* icon in the menu and click **"Hide from contacts"**. (This will move them into the *"Other contacts"* list.)
7. In your mobile phone, check the sync to make sure the archived contacts have disappeared from the phone's contact list.

If you wish to add any contact back, just search for it in the **"Google Contacts"** website. Select the contact under **"Other contacts"** and click **"Add to contacts"**. This will bring the contact back into your phone's contact list.
> 3 votes

# Answer
I have found one solution: have multiple accounts, your primary and backup/archive. Use the new Google contacts app to bulk select and move the contacts to the archive account. Then set either contacts app, either the stock app or the new cloud one, to only show the primary contacts. But Karthiks answer above is better.
> 2 votes

---
Tags: google-contacts, cloud
---


# Question
Title: I cannot hear Google maps voice after update
After the last update, I cannot hear Google Maps voice while navigating. I only get a nerve breaking bell like sound every time I am close to a turn. I cannot see anything obvious in the settings on how to fix that.

Why did this happen and what can I do to change it back to voice navigation?

My OS is android 6.0 (LG G4 device)

# Answer
Found why this was happening. I suppose that after an update voice through bluetooth option was selected automatically. Since I didn't have (never had actually) any bluetooth device, no voice could be heard.

Fixed this by going to google maps settings and deselecting voice through bluetooth option.

hope this helps others with a similar problem.
> 2 votes

# Answer
I just had a similar problem - Google Maps suddenly no longer gave driving instructions via voice. In my case the problem was fixed by going to Settings (Android Settings, not Google Maps Settings) - Sounds and Vibrations - Volume. The volume for Media was set to zero, I have no idea how that happened. Anyway, after pushing it up to about 70% then all was well again.
> 1 votes

# Answer
I just fixed this by deleting Google Maps updates. It's the updates that are the problem apparently. Without the updates I get sound when I click on the microphone icon in the top banner, but with the updates installed all that happens when I do that is that a drop down window shows some distances and nothing turns the sound on. So delete the updates and then set Google Play not to update the program. Wish Google would fix this because the updates would probably be helpful if not for this bug.
> 1 votes

# Answer
First check with Aux or Bluetooth, if you are having same issues

Second, go to Settings - System – Language and input – Text-to-speech options. Then under the Preferred text-to-speech engine, check if certain language is selected; if not, select Language. Clear cache and check again.
> 0 votes

# Answer
If you turn down the radio volume when the satnav is giving instructions you actually turn of the satnav volume. Wait to you think the satnav is giving instructions and turn up the volume. The voice should then return. Therefore, don’t reduce radio volume when satnav is talking.
> 0 votes

---
Tags: google-maps
---


# Question
Title: How can I transfer the numbers from my old Android phone onto my new iPhone if I lost the old Android phone?
I lost my old android phone. Decided to try out an iphone just to get literate. I'm wondering what the process is for transferring my contacts from my old android phone (which i don't have access to) to my new iphone.

I'm using Verizon as a provider, so might be able to leverage their cloud, though I am not sure if that's an option. I'm wondering if anyone else has done this before, and / or knows of a standard way to go about it.

# Answer
> 1 votes
I was able to accomplish this on my iphone through google.

1. I went into the Settings App of my iphone
2. Went into the Passwords & Accounts section, and hit the Add Account button which allowed me to add my google account,
3. A screen popped up which let me choose what to pull over (mail, contacts, calendars). Via this method, i was able to update my phone with all my old contacts.

I was able to do this because android had either auto-backed up my contacts through one of my google apps, or because i had initiated that process manually in the past (don't remember which).

# Answer
> 1 votes
If you were syncing contacts with your Google account you can login to your google.com account. In the top-right corner, just left of your photo there is a menu, where you choose "Contacts". You can browse your contacts there and even export them in CSV format.

You can than import these contacts to your Apple Accounts and voilà, sync iPhone with the account.

Please note that CSV import in Apple Account is limited to few contacts at a time, so without programming the procedure is practical only for relatively small number of contacts.

I wonder if there is an iPhone app that would sync directly with Google Account - good candidates are Outlook Client and some other e-mail clients that can use gmail. If you find something like that please post another answer to help others.

---
Tags: applications, data-recovery, data-transfer, ios, verizon
---


# Question
Title: Xiaomi A2 stuck in a reboot loop because of data partition
I installed the October 2020 update for my Xiaomi A2, and then it entered a reboot loop, giving me a "Cannot load Android system" message.

Actually, when I boot up the phone, I automatically get to the recovery menu, which only gives me two options: wipe the data partition, or reboot. And rebooting sends me back to the recovery menu.

Here's what I did:

* First, using fastboot, I reinstalled the entire OS except the data partition. That ended up in the same reboot loop.
* Then, using TWRP and executing it with `fastboot boot twrp-3.4.0-1-jasmine_sprout.img` I could `adb shell` into my device. From there I ran an `fsck -f` which did find a couple inode problem. But fixing those problems still did yield the same reboot loop.
* Using TWRP again, I locally cloned my data partition using `adb pull /dev/block/mmcblk0p69 data.img`, then I tried the "wipe the data partition" option. My phone did reboot properly, but of course it was reset to factory settings.

Question: is there a way I can restore my phone to a working state with my previous data? I really don't want to reconfigure all of it…

Also I don't really understand what's the problem with my original data partition. Is there a way to know why Android doesn't want to boot with it and why it sends me to the recovery partition?

More info:

* Running `fsck` on the local `data.img` says it has no error whatsoever
* I can mount the `data.img` and browse it. It's full of, well, files!

# Answer
> 1 votes
So, here's the best I could do:

* Try to boot normally
* The phone will crash and try to reboot to the recovery partition.
* At that very instant, press volume down and power, so that it goes to fastboot instead
* From fastboot, launch TWRP with `fastboot boot twrp-3.4.0-1-jasmine_sprout.img`
* Once in TWRP, get a shell using `adb shell`
* Then from this shell, look at the file `/sys/fs/pstore/console-ramoops-0`. It contains the **previous** kernel boot log!

In my case, here's what the boot log contains : `init: Rebooting into recovery, reason: enablefilecrypto_faile`. So apparently something is wrong with Androi File-Based Encryption

---
Tags: adb, recovery-mode, fastboot, ota-update, partitions
---


title: Android cannot forward packets

text:
# Question
Title: Android cannot forward packets
### Target:

Perform IP forwarding for devices within the same local network. (The real target is transparent proxy but the IP forwarding is a prerequisite)

### Network setup:

All devices are in the same local network `192.168.0.0/16`.

* main router `192.168.1.1`
* Android phone `192.168.2.1` (network interface `wlan0`)
* computer `192.168.2.10` gateway set as `192.168.2.1`
* others like Raspberry Pi at `192.168.1.11`

### Android setup:

* Data disabled, only WiFi connects.
* rooted Android 10 (Pixel 2 XL)
* enabled ip forwarding by `sysctl -w net.ipv4.ip_forward=1`
* netfilter: on all tables of nat, mangle, filter and raw, run `iptables -F -t <table_name>` and `iptables -X -t <table_name>`
* rp\_filter: Disable by `sysctl -w net.ipv4.conf.all.rp_filter=0` and `sysctl -w net.ipv4.conf.wlan0.rp_filter=0`

### Result:

* the computer cannot access to the Internet, `ping`, `dig`, browser, nothing works.
* the computer connects to local devices without any problem (like ping router `192.168.1.1`, SSH to the Raspberry Pi, or use FireFox through the SOCK5 proxy hosted on the Pi).
* Android phone connects to the Internet perfectly.

### Debug:

* using `iptables -t <table_name> -L -v` to show packet count, all chains have some packets, \*except the `FORWARD` chain of both `raw`, `mangle` tables shows `Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)`. After some googling, rp\_filter is the suspect but I'm sure it's turned off.

# Answer
> 0 votes
Thanks to @Irfan Latif, I found the solution myself. It's right that packets are sent to the last `unreachable` rule of `ip rule`, because they fail to match any previous rules:

```
# result of `ip rule`
... (no rules match)
22000:  from all fwmark 0x0/0xffff iif lo lookup wlan0
32000:  from all unreachable

```

So I added a rule to route incoming traffic from local network to route table `wlan0` by:
`ip rule add from 192.168.0.0/16 iif wlan0 table wlan0`

---
Tags: linux, networking, iptables
---


# Question
Title: How to Retrieve SD Card Files via fastboot or recovery?
I have a Nexus 4 (LG E960) running rooted stock 4.2.2/JDQ39. The phone fell from a foot high and the screen cracked. The touchscreen no longer works.

I have a full Nandroid (TWRP type) backup under /storage/emulated/0/TWRP which I want to retrieve to install in the replacement phone.

I can connect via fastboot but I cannot connect via ADB (neither via Command-line OR Wug's Nexus Root Toolkit). ClockWorkMod v6.0.2.3 does not give the option to mount USB storage.

**I need to retrieve those files. I need to either connect via ADB (in recovery or use fastboot to enable ADB in booted up mode) OR mount USB storage. What are my options?**

PS: This thread on XDA Dev does not help in my case as I do not want to erase my phone.

# Answer
> 1 votes
Often fastboot drivers are different from the ones used by Recovery mode and/or fully-booted Android system. I would recommend re-installing the USB drivers on your PC. You may need to delete existing drivers that Windows picked up. Full instructions with driver download for Nexus 4 here:

Quote:

> * Plug your phone into your computer.
> * Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
> * Right click on your phone and select "Uninstall."
> * In the box that appears, check the option to "Delete the driver software for this device."
> * Go back to Device Manager and refresh.
> * Locate your phone and right click to select "Update Driver Software."
> * Manually install the drivers by picking the folder of the files you downloaded.
> * Unplug your phone and restart your computer.
> * Plug it back in and everything should work.
>
> Download link: http://www.mediafire.com/?8xb50uktar8096i

# Answer
> 0 votes
A very late answer, I know, but a viable alternative approach:

**Use a USB-OTG (On-the-Go) cable** to connect a mouse to your phone, so you can work around the non-functional touch screen. You may then be able to upload your data out of the phone, and perhaps even connect a USB hub to have both a mouse and a USB stick (and a keyboard?) accessible "locally" on the phone, in case uploading data is not an option for you.

---
Tags: usb, adb, clockworkmod-recovery, fastboot, mount
---


# Question
Title: Transfer data from desktop to an emulator
I have some items in my ubuntu 12.04 desktop. I want to transfer them into the Sdcard of one of the avds in my android emulator (android-sdk-linux) which I have installed on the same system.

Like to know how to do the above.

# Answer
> 25 votes
**1. Using command line:** Here's how you can copy files to an SD card image.

You have to use `adb push` to copy files from Desktop to Emulator and `adb pull` for the reverse. Here's the syntax to copy files to or from an Emulator/Device Instance:

Copy from desktop to emulator:

```
adb push <local> <remote>

```

Copy from emulator to desktop:

```
adb pull <remote> <local>

```

Here `<local>` is path of file / folder on your desktop and `<remote>` is path of file / folder on your emulator.

Here is an example:

```
adb push foo.txt /sdcard/foo.txt

```

foo.txt will be pushed (copied) to the emulator.

---

**2. Using DDMS UI:** Here's how to work with emulator's file system using DDMS.

1. In the Devices tab, select the emulator that you want to view the file system for.
2. To copy a file from the device, locate the file in the File Explorer and click the Pull file button.
3. To copy a file to the device, click the Push file button on the File Explorer tab.

I personally prefer the adb pull and adb push commands as you can copy multiple files (in a single directory) with just one line command, using DDMS you can copy only one file at a time (no directory).

# Answer
> 1 votes
To transfer data from desktop to an emulator's SdCard on Linux do this:

* Create the SD Card:

Let's create a 64MB sd card for our Android emulator. From a terminal do this:

```
# cd ~/android-sdk-linux/tools
# ./mksdcard 64M ~/Desktop/sdcard.iso

```
* Now you can use the 'Eclipse Android SDK and AVD Manager' to create a new Android virtual device that can use the path to the sd card you created.
* Write Data to the SD Card:

From a terminal:

```
# cd ~/android-sdk-linux/tools
# ./ddms

```
* This will start the Dalvik Debug Monitor Server. Then:

1. Launch your AVD with SD card from Eclipse that you created earlier
    2. From DDMS, go to 'Device -\> File Explorer'
    3. Select the 'sdcard' folder
    4. Click the 'push file onto device' button
    5. Find your file and click open
    6. That's it!

Now from inside your code you can get to the sd card's path with:

```
Environment.getExternalStorageDirectory()

```

More you can read here.

# Answer
> 0 votes
You can also upload the file to your online drive of choice and share it to anyone with the link, copy and paste the link into the browser of the emulator and download it that way.

---
Tags: android-emulator
---


# Question
Title: How to remove rounded black corners which appeared after system upgrade?
I recently let my Nokia 3.1 to upgrade to Android 10. I don't know if it's Nokia's will or Google's but rounded black corners appeared on my screen, and are kept permanently visible during any app runtime. Is there a way to remove this feature ? I have found nothing in the system configuration menus. I also tried some app implementing custom corners but apart to add another layer of corners, it can't remove the ones I initially want to disappear.

Some pictures:

The rounded corners don't appear in screenshots.

# Answer
> 3 votes
Found this on reddit (thanks to "jyapayne"):

```
adb shell settings put secure sysui_rounded_size 1
adb shell settings put secure sysui_rounded_content_padding 5

```

First line is the corner "roundness" and second line ist the padding of the status-bar elements to the edge.

The Thread

---
Tags: screen, android-10
---


# Question
Title: SD won't encrypt or decrypt or work after removing phone battery
I removed my phone battery when the phone was on without turning it off first, my SD card was encrypted, so now I cannot access my SD card contents on my phone while phone detects the SD card.

Moreover, when I turn my phone on, encryption page shows after boot, giving me the option to encrypt or decrypt the sd card and selecting either encrypt or decrypt won't do anything.

So how can I decrypt my SD card and access my data?

My phone uses android version 6

# Answer
> 1 votes
First, apparently, the phone thinks that the SD card is in the middle of encrypting/decrypting so it will not allow access to SD card while not encrypting/decrypting the SD card either.

to remedy this I removed a `.MetaEcfsFile` on my SD card using my computer, after removing this my phone now thinks that the SD card is not encrypted.

Second, I encrypted my already encrypted SD card, the reason that this will not corrupt my data is that starting with Android 5, android uses fast encryption that will only encrypt edited blocks, so enabling encryption will not encrypt your files the second time if you don't change them.

From source.android.com:

> Full-disk encryption was introduced to Android in 4.4, but Android 5.0 introduced these new features:
>
> * Created fast encryption, which only encrypts used blocks on the data partition to avoid first boot taking a long time. Only ext4 and f2fs filesystems currently support fast encryption.

Last, after encryption you decrypt the SD card, android now decrypts the whole SD card not just changed blocks and you can access your files.

I also observed that removing the pattern and lock screen will not make your SD card data inaccessible.

# Answer
> 0 votes
I had the same problem on a Samsung Galaxy J5 (Android 6.0.1). I am not sure how it happened but I could not see my encrypted microSD card and could not decrypt it. The solution of mohas did not work for me but I managed otherwise:

* Plug the microSD on a computer and transfer the encrypted data to the computer (they won't be readable but they can be copied)
* Quick format the microSD card on the computer (format Fat32)
* Put back the microSD card in the phone (it should now be readable)
* Encrypt the microSD card on the phone
* Unmount the microSD card and plug it back on the computer
* Transfer back all encrypted data to the encrypted microSD card and plug the card back in the phone
* Now, you should be able to have access to the data on your phone (at least it worked for me)

---
Tags: 6.0-marshmallow, sd-card, encryption, samsung-galaxy-j5
---


# Question
Title: Can't change the language when phone screen locked
I am using Samsung Galaxy Core. I have given Password to my mobile in English. Today for some reason I changed my Language to TAMIL and forgot to change back to English. My Phone got locked when i try to give the password the keyboard appears in Tamil and I can't do anything. How can I change it

# Answer
Press the space button and hold the English language, and other languages will appear. Choose the language as you like and it will change the language.
> 0 votes

# Answer
If you have registered on Samsung. Then log in to your account using other computer. And reset Samsung mobile.

Now first tell me have enabled find my device on your mobile. If yes then log in to your account on any device and you an unlock your devices. Hope this can solve your problem.
> 0 votes

# Answer
Get a wired keyboard and plug it into the phone using OTG. It is working for me.
> 0 votes

# Answer
I had the same issue that I was unable to login into my phone due to the default language (keyboard layout) being non-English. The bad thing is when you try to change the language preference (by pressing space and hold) it again asks you for the password. The problem repeats itself. I solved this problem in this way:

1. I login into "safe mode" first (follow the link to the official Samsung Support).

2. Then I changed the default keyboard layout into Samsung keyboard (which is English)
3. Then I restarted it. This time the keyboard is English.
> 0 votes

---
Tags: lock-screens
---


# Question
Title: Understanding the sending of commands in adb shell
I am trying to talk to the modem embedded within a module through `adb` shell but since I'm accessing the HW remotely, i'm not sure of the original setup and may need some help clarifying:

`adb` shell runs in linux and following is how I was able to run the command:

```
cat /dev/smd0 &
echo -e "AT\r" > /dev/smd0

```
* what's the main point behind the first line with `&`? Doesn't that run things in the background? How does removing it not output the result to the terminal?
* the interpretation of the second line: writes/sends the string to the application processor from the linux host over `smd0` AT port. Is that legit?

# Answer
the 2nd line sends a request to serial. the 1st line is waiting for result. in order to make this work one must listening before sending request, that way the answer can not missed. one can accomplish that by running the listening process in background while sending request in same time. it is usual like for handling of named pipes
> 1 votes

---
Tags: adb, linux
---


title: Authenticator app is not working

text:
# Question
Title: Authenticator app is not working
I'm choosing option to add MFA in the Google accounts, scanning barcode, secret is added. Name of the account in the Authenticator is correct. However, when I try to enter the generated code - Google says it's incorrect. The same on all attempts.
Ideas?

UPD I've tried syncing time from the Authenticator - still getting errors

UPD2 Can it be the reason that I previously had Authenticator installed on another phone with different email?

# Answer
> 1 votes
Have you tried the following (taken from Google Authenticator site:

> **My Google Authenticator codes aren’t working (Android)**
>
> This might be because the time on your Google Authenticator app is not synced correctly.
>
> To make sure that you have the correct time:
>
> 1. Go to the main menu on the Google Authenticator app
> 2. Click Settings
> 3. Click Time correction for codes
> 4. Click Sync now
>
> On the next screen, the app will confirm that the time has been synced, and you should now be able to use your verification codes to sign in. The sync will only affect the internal time of your Google Authenticator app, and will not change your device’s Date & Time settings.

# Answer
> 1 votes
Your codes are most likely TOTP codes meaning they are time based. The simple fix is to to make sure all your devices are using the correct timezone (time is setup correctly). If the time on your devices are correct, but you are still having problems its most likely the browser.

# Answer
> 0 votes
I had similar trouble when I got a new phone. The app was installed on the new device (because apps were synced with the cloud) and it created codes but they were rejected by the google services on a PC. This helped:

* on the PC: log in to google once with a different method
* go to account settings \> security \> login to google \> 2-step-verification \> Authenticator App \> change smartphone \> android =\> a QR code is shown.
* on the smartphone: open Google Authenticator \> click on "+" button \> scan barcode
* scan the QR code from the PC

this created a new account in the authenticator app, creating different (correct) codes

---
Tags: google-authenticator
---


# Question
Title: How can I boost the volume on my Droid's speaker?
I used to have an app for my Treo called "Volume Care" that let me boost the volume of my speaker beyond what the factory settings allowed. Is there any app or hack that would allow me to push my Droids speaker further than Motorola wants to allow?

**Edit:** I thought I was clear before, but let me clarify. **I am not looking for just any volume control app**, I have one, I know of many, and believe it or not I am capable of searching the market for the word "volume." I am specifically looking for a solution that will allow me to **push the volume out of my speaker past that current manufacturer set limits.**

**Update:** I just added a bounty so I'll add a bit more clarification. I have seen apps out there that work with HTC phones only. This solution/app/hack must work on the Original Moto Droid rooted or not, I want a noticeable increase in the volume.

# Answer
> 1 votes
It seems that Android DSP apps all do different things and you'll have to try different ones to see if they work for your particular phone and ROM. I haven't had any luck tracking down why this is the case, or even what the apps are doing. One time I even tried modifying a config file that by all appearances controlled volume levels, to no avail.

I have found one that works for my Note II running OctOS L, and it's called Volume Booster. It's ad supported, and occasionally stops working, but it's great. I boost about 25 - 30%, which is loud enough to hear music across a room at a decent level. At that level, there are sometimes some distortions. Also, I think it negatively impacts phone audio, but since I don't make many calls, I haven't looked into this problem.

Given the distortion, I think that this app meets your requirement to get louder than the manufacturer intended. I presume that if I boost too much with this app, it will blow the speaker.

From the Play store:

> Simple, small, free app to boost your speaker or headphone sound volume. Useful for movies, audio books and music.
>
> Use at your own risk. Playing audio at high volumes, especially for a prolonged amount of time, can destroy speakers and/or damage hearing. Some users HAVE reported destroyed speakers and earphones. If you hear distorted audio, lower the volume (but it may be too late).
>
> By installing this application you agree that you will not hold its developer responsible for any damage to hardware or hearing, and you are using it at your own risk. Consider this to be experimental software.
>
> Not all devices support this software. Try it at your own risk and see if yours works.
>
> This app does not work on most 4.2.1-4.3 devices. It should work on 4.4 and higher, as well as on devices below 4.2.1.
>
> This is not for adjusting the speakerphone volume in phone calls (that has its own boost, I think), but for adjusting the volume of music, movies and apps.
>
> When you set the boost to zero, Volume Booster will be off. The notification icon is just for ease of launching. If you don't like seeing the notification icon when Volume Booster is off, just go to Volume Booster's Settings and set it to appear only when Volume Booster is running.

# Answer
> 1 votes
Magisk modules are the answer to your solution, but which one depends on a trial and error method. Viper4Android & Dolby Atmos are the 2 options that come to mind.

---
Tags: motorola-droid, volume-control
---


# Question
Title: The command 'adb root' works, but 'adb remount' results in "Operation not permitted" message
I'm trying to remount `/system` to copy some files to it. I tried the following with `adb`:

```
adb root
adb remount

```

The first command works fine (because my phone is rooted), but the second tells me that the operation is not permitted. If I open an `adb shell` and run `su` I can access the system folder without problems.

What could be the problem?

# Answer
Some phones just don't allow remounting via `adb remount`.

Mount as RW:

```
adb shell su -c "mount -o rw,remount,rw /system"

```

Mount as RO:

```
adb shell su -c "mount -o ro,remount,ro /system"

```

Also you could use the Adbd Insecure app, but it's not free.
> 4 votes

# Answer
Some builds require the following adb commands to be run first

```
adb root
adb disable-verity
adb reboot

```

Then once device reboots,

```
adb root
adb remount

```
> 2 votes

# Answer
Could be that SELinux getting in the way. Try this:

```
getenforce

```

If it returns `1` or `Enable`, do:

```
setenforce 0

```

Then try your command again.
> 1 votes

# Answer
This seems to usually work for me:

```
adb root

```

You will see a message as `Restarting adbd as root`. Unplug the device from USB, connect again and enter:

```
adb remount

```

**Troubleshooting:**

```
adb shell

```

Confirm that you are root if you see `#` shell prompt.
> 0 votes

# Answer
AFAIK, some devices have permanent (kernel-level I think) write-protection for the `/system` mount, so even if you're root, you still can't remount it in RW mode. You have to restart the device without this protection, which is done differently depending on the device.
> 0 votes

# Answer
I get the same error if I try to use `adb remount`. The reason is some kind of protection but can be bypassed by using a root shell.

The following should work (you may type `exit` to quit the shell):

```
adb shell
su -
mount -o remount,rw /system

```
> 0 votes

# Answer
Get adbd insecure from google play store. It helps give write access to custom ROMs that have it secured my the manufacturers.
> 0 votes

# Answer
**Problem statement** From the terminal, I connected to my STB using ADB connect IP address of the STB and after executing ADB root, I tried executing ADB remount. I was stuck with the below error message in my terminal.

Android 9 userdebug version execute ADB remount appear: remount of the / superblock failed: Permission denied remount failed

**Pre-requisite:** The first thing is you need to carry out the below pre-requisite setup,

* Need to have a laptop either Mac or windows with ADB installed or in case it's not installed get it downloaded from ADB but if you have windows well and good.
* USB to USB Male( Male -2- Mable cable).
* One end of the USB is connected to the STB USB port (White Color port) and then another end is connected to your laptop USB port.
* After the above setup is completed, from your command prompt or terminal type adb devices, if it lists the device connected with its serial number that means your connection setup is perfect.

**Solution**

* **First** thing from the terminal type below command adb reboot fastboot //This will reboot your STB fastboot flashing unlock // After STB reboots and you see the google android preloader, run this command fastboot reboot //After the above command execute this.
* **Next** adb root //After STB reboots and you see the google android preloader, run this command adb disable-verity //Immediately after that run this command adb reboot //Immediately after that run this command
* **Last** //disable Selinux and mount dir adb root //After STB reboots and you see the google android preloader, run this command adb shell setenforce 0 //Immediately after that run this command adb remount //Immediately after that run this command
* After the last set of commands you could see the remount works successfully, now either reboot your STB ie adb reboot
> 0 votes

# Answer
Try running the command `reboot disemmcwp` and re-rooting after the reboot. Then do your thing
> -1 votes

---
Tags: adb
---


# Question
Title: Why downloading updates in android ask wifi connection rather than mobile data?
Why did downloading updates in android ask wifi connection rather than mobile data?

# Answer
The size of update package is generally large so it by default uses only wifi rather than mobile data so that no money is deducted in case the mobile data is exhausted or there is no data plan.

## In old devices

Go to setings --\> About device --\> software updates. Here you disable the option download software updates via WiFi and enable , automatically download software updates or select manually update.

## In new devices

If you're using a new device after clicking on check for updates ,you'll get a alert or popup showing what's the latest update, in most of the cases you will find a checkbox ticked against download using WiFi only, just disable the check box. If this is not the case then on the screen where you download the updates there should be three dots in upper right corner, you will be sure to find the option to change data usage preference there.
> 2 votes

---
Tags: wi-fi
---


# Question
Title: Drag'n'drop event moving gone in Calendar... again
*Google Calendar's event's drag'n'drop functionality* stopped working... again, after nearly exactly two years since previous report. Tried to restart both Google Calendar and phone itself (Motorola Moto Z2 Play with Android 8.0.0), cleared app cache and then data, without any results.

I did very little to my phone before that happened:

* no configuration changed,
* nothing actually doing with my phone.

I have only installed one new up -- FakeStandby -- as suggested here, but since this app has nothing to do with the calendar itself, I would be surprised, if that would be a source of the problem.

To clarify problem:

*On a day view (not: agenda) long-pressing any event now brings no effect. Previously it caused an event box to be risen up visually above others, and moving finger around screen allowed to move event to some other hour or day. Now, drag'n'drop functionality does not exist / does nothing.*

Is there any know report about some bug, bug's regression or is this a generally known problem? Or is this again my stupid phone going wako in exactly the same way during second anniversary of the moment, this problem appeared for the first time?

**EDIT**: *From what I have learned, when Calendar becomes "locked" (no event's drag'n'drop) all items in calendar are visually more flat than usual. When functionality "returns" they again become a little bit 3D-like.*

# Answer
> 0 votes
On contrary to initial believes, it was (is) FakeStandby that is causing these problems!

This app is designed to FakeStandby mode, by turning off screen, but not causing actual standby mode. This causes that all other apps are not notified about phone being in standby and continue working in background (below FakeStandby).

To achieve this, FakeStandby must be able to control all apps (at least that's what its author claims). And in order to do so, it adds itself to the "Accessibility" section of the configuration:

And... that's all. Having *FakeStandby Service* turned off causes Google Calendar application to lose / disable / turn off event's drag'n'drop functionality. Why? Unfortunately, I have no idea.

The simplest workaround -- for having Google Calendar's full functionality and not being forced to uninstall FakeStandby -- is to kill this app after each use. *Long-press on its icon \> App Info \> Force Stop* does the magic. Until next run of FakeStandby, Google Calendar will have full functionality.

Since this is a system service, killing it with *Force Stop* will also automatically reset its setting in *Accessibility \> Downloaded Services* to *Off*. When you run FakeStandby next time and attempt to activate it (by pressing its button on the right side of the screen) you will see a message:

If this is too annoying for you or impractical, because you're using FakeStandby too often then I think there is no other option rather than a split decision:

* find some FakeStandby replacement or
* stop using drag'n'drop functionality in Google Calendar.

I am pretty sure that this is some kind of bug in FakeStandby itself, not in Google Calendar. As I have two other apps listed in *Accessibility \> Downloaded Services* (namely: Nova Launcher and Kaspersky Safe Kids). Both apps has their setting set to *Off* by default (because ability to observe screen and control other apps is used in them only in a rare, specific scenarios).

But, I have just managed to test that setting it to *On* for any of these two does not cause described problems with Google Calendar. So this got to be "something" in between FakeStandby and Oreo (I have no ability to test this issue in other versions of Android system).

---
Tags: 8.0-oreo, google-calendar, motorola-moto-z2-play, drag-n-drop
---


# Question
Title: Getting root access on meizu x8 (Andriod 8.1.0)
I tried various methods that I can found on the web to get root access, but none of them worked. I do not trust the vendor-provided method of getting root access. Does anyone know a way to get root access on meizu x8?

# Answer
**Disclaimer: I take no responsibility on the steps below. Root at your own risk.**

**As per Aayush's comment, I would advice you to read up more on rooting. Make sure you understand the ins and outs and the consequences of rooting, nd the possibility of bricking your device, before you attempt to root.**

1. Install Magisk Manager on your device.
2. Copy the boot.img to your device.
3. Run Magisk Manager.
    1. On the right near Magisk click on Install.
    2. Untick Recovery Mode.
    3. Click on NEXT.
    4. Tick the "Select and Patch a File"
    5. Now select the boot.img file you copied to your device. This will patch the file and save it to you Download folder.
    6. Copy the patched file to your PC.
4. Enable USB debugging and OEM Unlocking in your developer settings.
5. Unlock the bootloader (usually this can be done in fastboot by running `fastboot flashing unlock`. If this doesn't work google "unlock bootloader" with your device name). **This will factory reset your device, you will loose all data.**
6. Flash the patched boot image file in fastboot `fastboot flash boot <path-to-the-patched=image-file>`.
7. Reboot your device `fastboot reboot`.
8. After setting up your device again, install again Magisk Manager on your device. And follow the directions. It will install the Magisk (**Note: it will install Magisk not Magisk Manager which you just installed yourself**) to your device and you should have root).

**GOOD LUCK**
> 2 votes

---
Tags: rooting
---


# Question
Title: Are non indian sims work in this mobile?
I recently my Indian fb friend bought a Samsung F41 mobile online. On the package seal, it's written "Indian SIM Cards only".

Are non indian sims work in this mobile?

# Answer
> 1 votes
The restriction only affect users the first time they activate the phone. In short, just for the first time you'll have to use an Indian sim and afterwards you can use any sim card from any part of the world.

Source - Samsung: We don’t region-lock our phones (apart from when you first activate them)

---
Tags: sim-card
---


# Question
Title: How to disable sound during screenshot in Android 11 on Pixel 3?
I've already followed the steps here (although modified a bit, since I think that example wasn't using Android 11) to disable screenshot sound notifications:

But the setting seemed to have no effect.

There is still a sound whenever I take a screenshot by holding the power button and the Volume Down button.

How can I disable the sound?

# Answer
> 3 votes
This is not possible unless:

1. You have root access (delete the sound file), or
2. Use a 3rd-party trusted screenshot app, or
3. Disable system sound (yeah, it will disable notifications sounds and all too)

I'd recommend you to use a 3rd-party app (you can use power and volume button to take screenshots by the app by over-riding system's screenshot system). You can try Screenshot Assistant from F-Droid, or Screenshot or Screenshot sharer (super helpful if you don't use Google Assistant much) from F-Droid. FYI, F-Droid is super trusted.

> The Silence option refers to the notification you see with the preview of the screenshot. Try editing some other options in there (try making it alerting and then enable 'Pop on screen'). You will see what I mean. And yes, you're correct in saying that setting it as Silence or Alerting doesn't actually make a difference to the sound - it doesn't occur anyway.
>
> There is no user facing control to silence the sound emitted while the screenshot is being taken.

Source - Pixel Phone Help - How to turn off screenshot noise

---
Tags: screenshots, google-pixel, android-11
---


# Question
Title: How I can use SD card as internal memory?
I am using **Samsung Galaxy Prime+ - SM-G532F** device running Android 6.0.1. The problem I am facing is that. My device has very low internal memory, whenever I try to install more then 3 normal application an **error** encounters that please delete previous application to install other application.

So, I tried to find ways to use SD Card as app installation memory but problem is same there is not any option available in this device to migrate applications from internal storage to SD Card.

Please someone help me on this irritating problem

# Answer
If you buy a brand new Sdcard which you did not use or plug into another device, and insert it into your phone, you should get a notification that says something like this : "Use Sdcard as internal storage" . You can click that notification and accept it. It should now treat your Sdcard as as internal storage. Make sure that you do not remove that Sdcard after that.

Check this website for more information : https://www.nextpit.com/how-to-format-microsd-cards-as-internal-storage
> 1 votes

# Answer
First backup whatever you find valuable in your SD card. Next remove your SD card after power off. Insert it back and reboot. After in your status bar you will see option to set up sd card. Select use as internal. The reset process should start and viola. NB. YOU WON'T BE ABLE TO USE YOUR SD CARD WITH OTHER PHONES WITHOUT FORMATTING
> 0 votes

# Answer
Most of OEM's doesn't offer in gui option for adoptable storage. So you have to do it via ADB. Here is how

Here it is: NOTE all data on your SD card will be lost.

1. Make sure USB debugging is enabled in developer options under settings and then connect your phone to PC via USB cable.
2. Open terminal or command line on PC ( make sure you have ADB installed if not then download minimal ADB and fastboot, you can find it on Google click ) type command "**adb devices**" to make sure phone is detected, then type "**adb shell**" 3.Type '**sm list-disks**' to list the disks available, the result should be something like "*disk:179:160*"
3. To make SD adoptable use command "**sm partition disk:xxx:xxx private**" where *xxx:xxx* is replaced with result from previous command, in some cases there is **_** instead of **:** so watch out for that. If you want to use only half of SD as adoptable then use this command "**sm partition disk:xxx:xxx mixed 50**" and that's it.

If you want to move your data (pictures, videos etc) you can go to settings\>storage\>SD card\>more and you will have there option "migrate data" hit it and let it go.
> 0 votes

---
Tags: applications, samsung, insufficient-memory, adoptable-storage
---


# Question
Title: What are the various ways an Android phone can be locked?
I ask this question because the confusing terminology of different types of "locked" and "unlocked" like rooted and not rooted, Sim-locking, FRP locks, lock screens, ADB active debugging, and black listed phones, and even carrier locking. These are very confusing.

Can someone disambiguate this for me?

# Answer
> 4 votes
**Rooting** is the process to modify core OS components so that apps/processes can be run with high privileges (UID `0`).
See details in How Magisk works? and How to manually root a phone?

Rooting is not itself locked or unlocked. But **Unlocking Bootloader** is usually a prerequisite. Bootloaders are the initial components which load on device boot. OEMs lock them so that to restrict any deliberate or malicious changes to core OS components.
See Is there a way to root an Android phone without unlocking the bootloader?

Initially it was possible to unlock bootloaders just by issuing one or more `fastboot` \- Android's standard protocol to communicate with bootloader - (or equivalent) commands. However now many OEMs, including Google, add an extra layer over bootloader unlocking called **OEM Unlock**. It's a toggle switch in Developer Options (in Settings app) which is a prerequisite to bootloader unlocking. That is, a thief won't be able to unlock the bootloader and refresh the device to completely new state (e.g. by clearing FRP, see details below) until the screen lock is active.
Also some OEMs may require the user to get approval from OEM before bootloader unlocking, others may provide no option to unlock bootloader at all.

**Screen Lock** backed by a password or PIN or biometrics is the one we are all familiar with. It restricts unauthorized use of (at least many of) device features. On older devices this was only software-based. New devices provide hardware backends (like TEE and SE) to store credentials more securely.

**Factory Reset Protection** ties the Google (and/or OEM) account to the device. This info is saved to a secure place (usually a tiny partition) on the device and cannot be erased by doing factory reset, flashing ROM or flashing Factory Firmware. After Factory Reset user is asked to enter the previously entered account's credentials. So FRP is more focused on anti-theft protection. Some OEMs disable FRP when *OEM Unlocking* is enabled (but it doesn't matter when bootloader is unlocked).
Also some OEMs now go even beyond that, and they'd ask lockscreen or account credentials before performing Factory Reset.

**SIM Lock** can be either **SIM Card Lock** or another term for *Carrier Lock*. Former is independent of Android or the device it's being used in. SIMs are Secure Element chips i.e. they have their own processor and OS. You can set a PIN lock on SIM to restrict any unauthorized use.

**Carrier Lock** or **Network Lock** binds a phone (or some other device) to a carrier i.e. a service provider. This bond is usually a part of device purchase agreement, and may end after a fixed time period. There also exist ways to do *Carrier Unlock*, which may not be legitimate.
See How does carrier/network lock work? How is it implemented?.

Not sure in which context you are referring the term ***black listed phones***. IMEI blacklisted? IMEI is device's unique ID which the carriers may use to block a device from using their services after the device is reported lost or stolen or involved in some misconduct. IMEI/ESN blacklisted phones might or might not be unlockable depending on the reason of locking, the carrier's policy, and the availability of unlocking hacks.
See this answer for some details on device identifiers.

**ADB Debugging** is Android's standard way to let ROM and app developers communicate with Android device from a PC over USB or Wi-Fi connection. End users may also use ADB shell (like any other UNIX shell) to issue commands. ADB has no direct relation with any (un)locking mechanism.

---
Tags: rooting, lock-screens, bootloader-lock, sim-unlocking
---


# Question
Title: Why can't I delete a folder in /config/sdcardfs as root (Termux)?
I'm looking to delete a folder that is in `/config/sdcardfs`. My device is rooted and I'm trying as superuser. I still get the results `operation not permitted`.

What do I need to do to get the permission to do this.

I have tried to do `sudo rm -rf name-of-folder` with no success. I have also tried to do it after running `tsu` (Termux's version of `su`). No success.

**P.S.**
I haven't had any issues deleting in other places even in places I need root permission (for example in the `/data` folder.

# Answer
## SHORT ANSWER

You don't need to delete anything in `/config`. What appear inside the directory aren't actual files. They are cleared and repopulated on device restart.

You can't delete `/config/sdcardfs` directory. SDCard FileSystem (`sdcardfs`) is a core OS component. Your device (or at least storage) won't be usable without `sdcardfs` properly configured.

## DETAILS

Android is based on Linux kernel. Kernel is the backbone of OS which handles hardware components and many other core functionalities. The other part of OS: userspace talks to kernel space through different mechanisms like `syscalls`, `sockets` and virtual filesystems. `procfs`, `sysfs` and `configfs` are common virtual/pseudo filesystems i.e. they live in RAM. Kernel exports information about processes, hardware devices, and drivers etc. to user space through virtual files in these filesystems.

`/proc` and `/sys` are mostly read-only, except a few interfaces to which userspace can write some values in order to make configurations. `configfs` (which is mounted at `/config` on Android devices) is relatively a new addition to Linux kernel. It allows userspace to make relatively bigger kernel configurations by creating large number of virtual files in sub-directories under `/config`.

Android uses `configfs` at least for two purposes:

In order to make file sharing among apps possible, Android sets fixed permissions on files in external storage (be it physically internal or external). To achieve this, at start, Android used FUSE for filesystem emulation, then `sdcardfs` replaced it. For more details see my answer to What is /storage/emulated/0/? and Android's Storage Journey, in particular the concept of ***synthesized permissions***.

So it's the Android OS which creates and deletes virtual files in `/config/sdcardfs/` in order to let kernel know which permissions to enforce on which files/directories in external storage (`/sdcard` as well as physically external SD cards, USB drives etc).

Additionally Android uses `sdcardfs` to assign three GIDs: `AID_MEDIA_AUDIO (1055)`, `AID_MEDIA_VIDEO (1056)` and `AID_MEDIA_IMAGE (1057)` to media files by providing their relevant list of file extensions in `/config/sdcardfs/extensions/`. It's to quickly categorize files without scanning all of them. See some details in this answer.

So deleting something in `/config/sdcardfs` (and in kernel's other virtual filesystems as well) doesn't make sense if you don't know what you are doing. That would do no good except breaking storage functionality on your device.
> 1 votes

---
Tags: root-access, delete, termux
---


# Question
Title: How to send .apk file over mobile Gmail?
Since .apk is a regular executable file, I was more than sure that I will be able to trick mobile Gmail in the same way as I was able to trick PC version of Gmail years ago to force it to send a PC executable (.exe) which it prevented as well. Turned out, I was wrong.

Usually changing file extension to `.dat` or some other or compressing it with password (encrypting file) was enough for PC version of Gmail.

However, for mobile version, everything that I have ready at a hand and tried failed as well:

* sending as plain file (obviously),
* changing `.apk` extension to `.dat` or some other,
* compressing with ZIP with no password,
* compressing with ZIP (ultra compression) and encrypting archive with a password,
* compressing with 7ZIP (ultra compression) and encrypting archive with a password,
* using an 7 years old idea of double compression:

+ compress `.apk` file into `.zip` file without password,
    + compress resulting `.zip` file again into another `.zip` file with password / encryption.

If mobile Gmail is able to detect that I am sending `.apk` executable file even in 7zip compressed file with password (or it can prevent me from sending such file for any other reasons) do I have any option left? Is there any way to send `.apk` file over mobile Gmail (attach them to message composed in mobile Gmail)?

# Answer
> 1 votes
Blocking `.apk` files and encrypted archives as email attachments is clearly mentioned in GMail policy:

> To protect you against potential viruses and harmful software, Gmail doesn't allow you to attach certain types of files, including:
> ...
>
> * Password protected archives whose content is an archive

> To protect your account, Gmail doesn't allow you to attach certain types of files...:
> .ade, .adp, .apk, ...

So no one can help with that except Google. You can go with file sharing as suggested by others here, and Google as well:

> If you're sure the file is safe, you can ask the sender to upload the file to Google Drive. Then send it as a Drive attachment.

Source: https://support.google.com/mail/answer/6590

But if email attachment is the only option you want to go with, use GPG/PGP encryption which is very commonly used in emails, even to encrypt whole emails including subject and body. Many e-mail clients provide OpenPGP-compliant email security. On Android you can use Termux or OpenKeychain for GPG file encryption. Both are open-source and free (I've no affiliation with either).

---
Tags: gmail, apk, 8.0-oreo, motorola-moto-z2-play
---


# Question
Title: How can I delete from my smartphone the images downloaded by Google Chrome from the internet, which I can't find anywhere?
I have a A3 Umidigi smartphone, Android 9. I downloaded the images by Google Chrome (search images engine), and I can't find them in any folder (included Download, Pictures or DCIM), but I can see and use them as backgrounds (actually I use as background one of these downloaded, invisible images). I searched them using the App "Total Commander" (and other similar), and I connected the smartphone to the desktop by usb cable, but I couldn't find them. Google Chrome has access to the drive. Now, if I download another picture, Chrome asks me where to save it, but I have a dozen images I can't find.

Download folder (without the downloaded pictures).

Download options in Google Chrome (without the pictures).

"Background" selector: I can see and select the pictures (even offline). By the way I can't find any App named Background or whatsoever.

Root folder

Root/data/data folder

Root/system folder

data/com.android.chrome/files/Download folder (empty)

# Answer
In the folder `/data/data/com.android.chrome` and its subfolders, would be the place to look. You will need superuser permission to be able to access this folder. In Total Commander start File System Root.

For example `/data/data/com.android.chrome/cache/image_cache` Has picture files. Actually all the files in there are pics even though they have no extension.
> 0 votes

---
Tags: applications, chrome-for-android, google, downloading, images
---


# Question
Title: My play store suddenly change to another location and I cannot get it back
My play store used to be the US version and just a few days back it changed to Hong Kong version. Now I cannot figure out why and how it changed and I want to get it back to US version.

The only thing I can recall is that I used a proxy of HK those days. But now no matter how I set the proxy, my tablet, phone and the web page always give me the HK version.

I have read the posts about activating the play store of another country after relocate and I tried the methods, until now none of them works.

My account has two credit cards added, one's address is in US and the other is in Canada. Two of my apps that are only available in North America are not shown in neither \[INSTALLED\] nor in \[ALL APPS\] now.

The webpage version would show the US version as long as I logout my account, otherwise the HK version. The visible paid apps are all in HKD currency, which is rather disturbing!

Someone, please help me!

===UPDATE ON FEB 27, 2015===

The play store still shows HK version, however if I view games that are distributed to non-NA region (like EA's pvz\_row, or r3\_row) in the web page, it shows "The app is not supported in your device's country). Yet if I download a na version, the in-app-purchase currency shows HKD prices. I am confused, maybe I will have to contact Google play support team.

# Answer
> 0 votes
Clearing app data and cache of Google Play Store worked for me.

# Answer
> 0 votes
Try clearing your data of Google play Store and your Chrome browser and then put your phone's location on. Then go into chrome and accept the "chrome would like to use your location" (or something along those lines) and sign into your Google account. This fixed my problem.

---
Tags: google-play-store
---


# Question
Title: What is this icon in my status bar that looks like a finger pointing at 3 horizontal lines?
Can anyone identify this icon?

here again with context:

I can't find anything online and no one at Verizon or Kyocera can identify it either. I need help figuring out what this icon is and what it means.

I have contacted the Verizon Tech's, Kyocera and personally searched online, with no positive ID. Deleted all apps, factory reset, and even safe mode start up, and the icon remains at the top of the screen in the status bar. The only time the icon is not at the top of the screen is when you click on the drop down for the status bar icons. This phone is the newest Kyocera Duraforce Pro-2. Glove mode nor the underwater camera mode have any affect on the icon when switching these two selections on or off.

Any information on what this is would be greatly appreciated. Thank you for your time and help with this.

# Answer
> 4 votes
I mailed Kyocera linking this question and they replied very quickly.

**It is a Verizon security app** and Kyocera can't do a thing about it. Mail extract :

> Allow us to inform you that this Icon is for a Verizon security application running on the phone, please be aware that this will not affecting its functionality. At the moment there is no way to remove the Icon.

Screenshot of mail below. You would need to chase Verizon for more details as to what it does but being a device tied with them, I guess you have to live with it.

(Click to enlarge)

You can refer to the Tech Support Case Number: 00689640 and follow up with Kyocera (Phone.Help@kyocera.com) if you wish (The person who sent the email is Karla H, Technical Support Specialist).

# Answer
> 0 votes
Go into accessibility and turn off the "security and privacy" app and the icon will go away.

# Answer
> 0 votes
I went into accessibility and turned off "Digital Secure" and the icon went away.

# Answer
> 0 votes
Go to settings, apps and notifications, and then down to digital secure or safety and security and click on it. Then turn off all notifications and force stop it. The symbol should go away.

---
Tags: notification-icons, 8.1-oreo
---


# Question
Title: Is it possible to migrate an SD card formatted as adopted storage to a new phone without reformatting?
My phone (Moto X Pure 2015, a.k.a. Clark) hates me. It's a refurb that I doubt was properly fixed, which was a replacement for my last one that had a bad USB port, but the issues didn't start until post-warranty (both original and 90 day for refurb). My wife decided to get an iPhone, so now I have hers, which is also a refurb, but it still works correctly for the most part. I would like to migrate everything from my phone to hers...including the 64GB Micro SD card formatted as adopted storage...without formatting the card.

Is this possible? Are there any options that don't include extra memory cards, usb sticks, or computers? I know I can move everything to an intermediary storage device, or to a new card in the new phone, but if there's a way to do it without that extra step, that would be nice to know. I'm rooted and running nearly the latest Lineage OS nightly (4/3), if that makes a difference, and I'm open to things like key extraction if I can get a good guide on what I actually need to do.

# Answer
> 3 votes
Though you did not (yet) confirm both devices are rooted, this solution might be of interest for those where they are:

Following up to our adoptable-storage tag-wiki, you will find a link to How to decrypt adopted storage? Based on that, the following approach seems feasible:

1. From the original device, extract the encryption key file located in `/data/misc/vold`
2. Copy this file to the new device

There's a missing step, though: As the file has no fixed name, I assume this must be stored in some settings database. So that database entry must be found and added to the new device. On the other hand, the name might as well be derived from the label of the SD card it belongs to.

So basically, this answer might be incomplete – but the approach worth a try. If someone can provide the missing step, please do so in the comments and I'll integrate it here (with credits given, of course).

# Answer
> 1 votes
Tag wiki of the which you used is a good start point :

* When you adopted the external SD card, it is encrypted with a key that is unique - hardware key that is specific to your device ( not common to model). This means you cannot read the SD card on another device, even if same model.**According to the \[Android documentation\]\[1\] :**

> .. Keys are associated with adopted devices based on the adopted partition GUID.
> **..**
> Because the contents of an adopted storage device are strongly tied to the Android device that adopted it, the encryption keys should not be extractable from the parent device, and **therefore the storage device can't be mounted elsewhere.**

* In other words, you cannot separate the device and external SD card as separate entities to access memory - ( except when device is connected to a laptop )
* Technically, it is possible to retrieve the information contained in the card by recovering the key , in the absence of device. Foot note in the wiki offers a couple of methods but you would need access to a computer , which you do not wish to use
* There may be another catch - Samsung encryption may be proprietary and details are not made public

To sum it up, your best bet would be to transfer contents to a laptop, and transfer them to the external SD on your new device

**Edit:** If both devices are rooted there may be a way, which I am not aware of ( seeing Izzy's comment)

# Answer
> 0 votes
I'm sure a TWRP /data backup and restore to new device could do the trick as well if I'm not mistaken. Would be much simpler in my opinion.

---
Tags: root-access, adoptable-storage, lineageos, device-migration, moto-x-play
---


# Question
Title: Is there any way to save data i.e. Screenshot/ photo to external storage by default
I am using Moto G. It is Android 6.0. Internal storage 16Gb. Now I want to store all screenshot and photo/ video taken using default camera app and whatsapp/ other social media data to external storage.

What is problem: As I came to know the option to select "save to external memory" or selecting external memory as default is removed from android 6 and above.

I know there is no short of internal memory but I want to keep/ preserve these data on external card even if I remove/ swap the external card. say for legal purposes.

Now the problem is if I format external SD card as portable it there is no option to select this as default storage. If I format external SD card as internal storage I can not remove it without loosing data.

So Is there any way to make apps to save all data to external storage by default. I don't mind where apps are installed. Only I care about screenshots/ camera photo/ audio recording/ video recording/ whatsapp data etc.

Thank You all

# Answer
Try this solution: https://android.stackexchange.com/a/217936/218526

The Directory Binder option in Lucky Patcher might work as well. Haven't tried it out myself though, so no promises.
> 0 votes

---
Tags: 6.0-marshmallow, adoptable-storage, screenshots
---


# Question
Title: How to flash a custom rom on galaxy on5 pro
I'm an Android fan and I have a Samsung Galaxy On5 Pro. It is currently running Android Marshmallow `6.1`. I want it to get upgraded to Android Nougat `7.1.1`. I don't have a recovery. How can I install TWRP? How do I do it? Edit: I got TWRP and installed android nougat `7.1.1` How do I install android `8.1`?

# Answer
Root your device at your own risk!

1. Check your device model number. (for SM-G550FY/SM-G550T1/SM-G5500T2/SM-G5500 only)
2. Select TWRP Based on the mobile model number.
3. Make sure your device battery is charged above 50%
4. Backup your current files and data, just in case (save them on external storage).
5. Flash TWRP using odin
6. Install SuperSU.

For detailed information see https://www.androidinfotech.com/root-samsung-galaxy-on5-sm-g550-lollipop-marshmallow/ and https://rootmydevice.com/root-samsung-galaxy-on5-pro/
> 1 votes

---
Tags: 6.0-marshmallow, custom-roms, 7.1-nougat, 8.1-oreo
---


# Question
Title: I tested the "lock" feature on Android Device Manger, and now I can't unlock it
I was just testing out Android Device Manager and I tested the lock feature. I entered a password, as requested, and the phone was locked. I was told that since I already had a lock screen on my phone, the password wouldn't be needed. I went back to Android Device Manager and there is only a "lock" option, not an "unlock" option.

Now I can't access my phone since it won't allow me to enter the password on the phone, or unlock it from Android Device Manager.

# Answer
you have not mentioned which phone you are using, but i found this step in XDA forum, and this seems to have solved it. Could you check if one of the solution helps you: xda-adm-unlock, check out the post #3 by maysider. Here is the complete snip of the sollution from XDA:

> so the BUG is "made by Samsung". Samsung just do not accept any correct PIN or password (maybe because of "wrong" keyboard). could anyone tell me how to remove the lock without wipe? thx
>
> edit:
>
> solution 1) just if you have debugging mode on then follow this solution http://maxoberberger.net/blog/2013/08/unlock-android-device-using-adb/
>
> solution 2) just if you can change your keyboard for another (if you are allowed when entering password)
>
> solution 3) just if you have Samsung account, log into Samsung Dive \>\> "unlock" (my case)
>
> solution 4) no debuging mode + no keyboard solution + no samsung account? \>\> just and only wipe through recovery or Google Device Manager
>
> Happy now, but I was lucky
>
> SAMSUNG BUG in 100 %

HTH.

**Edit by Izzy:** The link with "solution 1" proposes changes made with ADB, which require root access:

```
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update secure set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
update secure set value=0 where name='lockscreen.lockedoutpermanently';
.quit
exit
adb reboot

```

This will unset your device lock completely, as if you did not have defined any.
> 0 votes

# Answer
Reset your phone with its buttons You can erase your locked phone using its power and volume buttons.

You first have to power off your android device. You will have to press and hold the volume down button along with the power button. Keep holding until you see Android images/buttons. Then release the buttons and then follow the volume down button to go for factory reset, afterward select the power button.

But this is a risky plan as you will lose all your data. After resetting when u will turn it on it will ask to set up your phone. After setting up you are completely ready to use your phone and from now on be alert do not put lock patterns if u easily forget them.
> 0 votes

---
Tags: lock-screens, android-device-manager
---


# Question
Title: Is there a way to give permissions temporarily?
Is there a way to take away permissions when i leave an app? i dont have root and also no intention to root. is it possible to do this with adb or something??

# Answer
> 3 votes
I have already asked this question Is there an alternative to Bouncer- Temporary app permissions?

I found a temporary solution.. using automate app. You can use its interact block to automate the steps real easy. But it only works when the element is visible. That means we will have to scroll manually. Rest all is easy!

---
Tags: privacy
---


# Question
Title: Can't register virtual US number with whatsapp business
I used to use a virtual US number for registering and using WhatsApp Business (for people i don't trust and don't want to give my personal number) But now whenever I try to register a new virtual number, it says it's an invalid number for USA. I have tried 2ndLine, text+ and few more apps.. Can anyone explain what's happening and provide a solution if possible..
Thanks in advance

# Answer
Yep.. Whatsapp business recently changed a few things.. But as far as ive tested it.. some virtual numbers still work from 2nd line and textnow(both are from same company ig). I mean 1 in 50 would work. Just give it a try!
> 1 votes

# Answer
Yes most virtual numbers have such restrictions, however you have a higher success rate if you use voice for verification instead of SMS, you cant even setup voicemail recording to retrieve the call playback.

If this fails get other similar virtual number provider like TalkU, you get credits by watching some ads, but the advantage is that you get to keep the number for the duration you're subscribing with credits (which you get from watching ads=free)
> 1 votes

---
Tags: whatsapp-messenger, voip
---


title: Change device model on Android 10

text:
# Question
Title: Change device model on Android 10
I have Realme X2 (RMX1992) phone with Lineage OS 17.1 with root. I want to change my device model to Realme X2 Pro (RMX1931).

I have edited `build.prop` files in `/system` and `/vendor` folders with `ro.product.model=RMX1931` and also set the global device name as below:

```
adb shell settings put global device_name RMX1931

```

But still, my device is still recognized as RMX1992.

How to change the device model?

# Answer
Below is the method worked for me to change my phone model to Samsung Galaxy S10+

1. You need to have Magisk for root access
2. Install BusyBox and "MagiskHide Props Config" Magisk module and reboot the phone
3. Install the below terminal or any of your choice https://play.google.com/store/apps/details?id=jackpal.androidterm
4. Open the terminal and type `props` to open MagiskHide Props Config and select option 5 to add/edit custom props values
5. `ro.product.model` and `ro.product.brand` values need to be changed to the desired phone model
6. Go back to the main menu and select option 3 to enable Device simulation for the values added in step 5 and then reboot the phone

After reboot, the phone model will change to the values added. You might also need to check build.prop file if any additional values to be added in the Props.

**Note:** Take a full backup of your phone before performing these steps in case of any issue occurs.
> 1 votes

---
Tags: android-10, builds, realme
---


title: Editing adb backup files

text:
# Question
Title: Editing adb backup files
I want to edit the contents of an `.adb` backup file. I found a command to extract the contents:

`dd if=mybackup.adb bs=24 skip=1 | zlib-flate -uncompress | tar xf -`

I edited the extracted files as needed but how do I build adb files with the modified files?

I thought of streaming the directory, compressing it with zlib-flate and generating the tar file. Is it possible?

# Answer
In my opinion the preferred way for extracting such backup archives is Android Backup Extractor (abe) (requires installed Java Runtime).

It allows to convert adb backup archives to tar files and also the reverse way to convert TAR files back to an adb backup files that can be restored via adb:

```
java -jar abe.jar unpack mybackup.ab mybackup.tar

```

Modify created file `mybackup.tar`.

```
java -jar abe.jar pack mybackup.tar mybackup_mod.ab
adb restore mybackup_mod.ab

```
> 3 votes

---
Tags: adb, backup
---


title: TWRP loop on booting nokia 3?

text:
# Question
Title: TWRP loop on booting nokia 3?
i successfully installed twrp but on twrp reboot i selected system and now on opening nokia 3 it goes to twrp. Only twrp can be opened not the OS (normal boot) of nokia 3.

I tried flashing stock rom of nokia 3 with sp flash tools but on starting or booting phone , it will not detect nokia 3 and red and yellow bars does not appear. so how to flash stock firmware when i am stuck boot looping in to Twrp. Any other way if possible please describe.

# Answer
As your question you install twrp recovery and did you perform wipe after that ? If not try this might work or try the following

1. Turn power of your phone in twrp recovery option by reboot\power off or hold the power button till it shuts down.
2. Now load stock rom in sp flash tool.
3. Now click on download button.
4. it will dectect your phone if your phone is power off and if battery is removable please remove it before connecting
5. now connect your phone with usb in one end and to other end with pc.
6. if it didn't dectect install the right mtk drivers.
7. after successful install your phone turns to stock os with stock recovery and will boot normally.

Alternative

1. Find custom os for your device.
2. move it to sd card.
3. flash it through twrp recovery.
4. then perform wipe and clean cache and boot normally.

Hope it works.
> 0 votes

# Answer
As You said when you installed TWRP on your Nokia 3. So, Its ovious Your phone can't boot into os. In TWRP Installation Guide Its Says "After Installing TWRP on your Phone your phone will not boot. it stuck in bootloop".

For this You Have to flash a file called "encrypt.zip" through TWRP to Your Phone. After This Your Phone again bootable to OS. and You don't need to Flash it. If you tried to Flash then, you are in big problem.

Thanks!
> 0 votes

---
Tags: twrp, boot-loop, nokia-3
---


# Question
Title: Why am I getting Google Drive notifications about strangers' documents?
Screenshot:

Is this just a new form of spam or phishing technique, basically betting that I'll click on the notification and look at the document? I haven't looked at any of them yet, but it seems utterly bizarre that Google Drive would notify me of the occurrence of anything in *someone else's document.*

A quick tour of the Russian alphabet and Google Translate reveals the document name as "Message No. FB-24".

Cross-post

# Answer
> 0 votes
This has happened to me more then once and always on a chromebook. (I don't own one anymore) Anyway I just wanted to say something because it was malware in my case.

---
Tags: notifications, malware, google-drive, push-notifications
---


# Question
Title: Brightness level stuck at minimum after upgrading to Android 5.1.1
I have Sony Xperia Z (C6603, 10.7.A.0.222) and the brightness level is stuck at minimum after update to 5.1.1.

I have tried:

* sensor test - light sensor is OK.
* set brightness via ADB (`settings put system screen_brightness 200`) - didn't work.
* using brightness control apps (like LUX for example) - didn't work.

Using stock ROM without root, any apps or functions that could set brightness to low for saving battery are either uninstalled or turned off? Any suggestions?

# Answer
> 0 votes
This happened to me on my galaxy note20 3 weeks ago. My screen went pretty dark. After a hour or so i saw on settings blue light filter was on. I did not turn it on. I had to shut it off then reset the phone.

---
Tags: 5.1-lollipop, sony-xperia-z, screen-brightness
---


# Question
Title: Company owned devices options for system apps
My questions regard the possibility to temperate which phone application could be set up while using Google Workspace (or any other MPA). Specifically: can I set up an application to replace the phone system app?

I've read this but does that means that I can't disable the phone system app? Or that the `com.android.phone` package **is** the system app.

Another solution would be to get controls over the default apps settings and lock the employee out of these ones. The MPA solution would then be able to enforce the use of another Phone App as being the default system one. I could not find any documentation covering this.

# Answer
My interpretation of https://support.google.com/a/answer/7292363 is that

`com.android.phone` **is a system app that cannot be disallowed**

However you can create a policy which will prevent non-emergency calls:

> 4.24. System radio management
>
> 4.24.5. IT admins can configure whether the device can make outgoing phone calls, excluding emergency calls (see outGoingCallsDisabled).

At which point you can put your own Phone app on the device. Note limitations on Phone apps that developers are bound to.

So presumably the device will still have the Google phone app but that app can only be used to call emergency services.
> 1 votes

---
Tags: system-apps
---


# Question
Title: HDR option grayed out on Samsung A50 camera
I can not turn on HDR. It is grayed out. I tried all modes front and rear camera and it is always Grayed out and I cant turn It on. I am using a Samsung Galaxy A50 that I recently bought and Samsung live chat support was not helpful. I am on the latest software.

# Answer
> 0 votes
As @Robert said in the above comment, I have switched from 3:4H (25 megapixels) to 3:4. And HDR now works.

# Answer
> 0 votes
I had the same problem when I was in the photo mode of the camera. After I switched to video mode and then went to the setting, then I could toggle the auto HDR.

---
Tags: settings, camera, 9.0-pie, samsung-galaxy-a5
---


# Question
Title: Google Play Games profile fails to change my game profile to public
I've been experiencing a problem with the 'Play Games' app from Google on my tablet.

When I go to my profile, I see a message showing me

> Your Game Profile is hidden
> Touch to change this setting

In order to make it public, I touch the option, and press the `Make Public` button. Then, I see a popup saying that my profile is being updated and then a toast appears telling that my profile has been updated.

However, when I go back and re-visit my profile, the message still persists meaning that my profile is *still* hidden.

Also, my friend told me that he can't see me in his 'Players' list even though he follows me on Google+. This means that my profile is not public.

So, **How do I make my profile public?**

My tablet is running Android Kitkat 4.4.2 and has all the apps (Including Google Play Games) updated.

# Answer
> 1 votes
In the `About me` section of your google profile is where you can make your profile public or private.

---
Tags: 4.4-kitkat, profiles, google-play-games
---


# Question
Title: Read data on SD card which was formated as Internal storage of Android OS
I have a Lenovo Vibe K5 Plus with Android 8.1.0. I plugged in a new SD card (Kingston MicroSDHC 32 GB) and this SD card was formatted as Internal storage, so data on this SD card was accessible by connecting the mobile phone to the PC.

However, yesterday I removed the SD card from my mobile phone and I did a big mistake that I clicked something in Settings -\> Storage, something like forget SD card. So now I have got an SD card with my data (photos, music, etc.) which I cannot read on a PC with an SD card reader.

Is there any chance to read my data from this SD card? I looked that in my phone some data has `.nomedia`.

# Answer
> 1 votes
The "forget" option tells the Android system you no longer have the card. What it then "forgets" is the encryption key needed to encrypt/decrypt this specific card. So basically you've locked the safe and threw away the keys; without the keys, there's no reasonable way to open the safe again.

Thus, your data are lost. It *might* be possible to regain the key (e.g. if the device is rooted; you could create an image of all its file systems and use forensic methods to find and extract the deleted key). But not only would that require your device to be rooted, the effort to find and extract the key is not low, and chances are it's meanwhile overwritten. If your data are worth a 4-digit value (EUR or USD) to you, you could contact a forensics company to give it a try – but chances are rather low.

Permit me a note to one of your comments on your question:

> I do not have any backups, because all worked properly.

That's exactly the point-in-time when one **does** perform a backup: you need the data intact. You cannot create good backups of a broken system – but at that point you'll need a backup to repair it, as we've just learned.

Also see: How to get Adoptable storage encryption key without root access after I “forget it” (answer: you can't).

---
Tags: external-sd, adoptable-storage
---


# Question
Title: Can one app access an app that has password protected?
On my Android, there is a feature that I can set password for app that I want to. Example, let's say I set a password for my gallery and then I install new app from play store or browser and the new app want to access my gallery. Can that new app access to my gallery?

# Answer
> 3 votes
No, The other app wont be able to access this app but other app can access this app data if its not stored encrypted on device storage. Other app only need storage permissions to do that. If other app can access device storage then that app can access any unencrypted data stored on device. But it wont be able to access OS files which are stored in read-only partitions/folder without having root access

---
Tags: permissions
---


title: Upgrading a locked Android 4.4.2

text:
# Question
Title: Upgrading a locked Android 4.4.2
I want to try to upgrade my Huawei Y560-U02 Android 4.4.2 to anything newer but it should at least be Android Lollipop.

I opened another thread in regards for this phone in order to get the firewall working on it but since that did not work I want to try to upgrade it properly.

I did not know the steps on how to do it properly and ended up causing some damage. There is a lot of information and steps on the internet and that is what lead to having some issues now. I have already backed up all the data that I need and ready to proceed.

So the Phone is Huawei Y56-U02 2015 Android 4.4.2 Kitkat. The phone is locked.

Because I did not know that phones need to be unlocked first it caused damage to my boot recovery mode. I can't access it anymore as it would just get stuck in that. Otherwise the phone is booting normally.

What I will need is to find a way to unlock it which I understand can be done if I unlock bootloader.

Please provide me with the best tips and steps to get this done.

I did try to use the built in Huawei updater but that just installed a different version of the same Rom.

Locked phone I mean locked ROM.

# Answer
> 0 votes
I managed to flash the phone with SPD Upgrade tool and now all is back to normal.

The damage has been repaired.

---
Tags: 4.4-kitkat, 5.0-lollipop, updates, bootloader, rom
---