EMUI 9 internal storage encrypted (Error 190) - Honor View 10 Questions & Answers

I finally managed to get to EMUI 9 and it seemed fine until certain apps threw an error 190 when installing them via the play store. Turns out I can't access the internal storage because it seems to be encrypted from a previous setup. How do I go about to fix this?

Related

[Q] Insufficient storage available (weird behaviour)

I am using a Samsung Galaxy Tab GT-P3110 (7.0") and I installed the cyanogenmod version 10.1.3-p3110 with the 3.0.31-CM-gac1803e kernel. Since today I am unable to install some apps. The app manager tells me I used up 2.6GB of the internal storage and Ive got 2.0GB free.
When I try to install the YouTube app or the Root Browser app the play store puts out an error telling: Insufficient storage available. However when I try to install the ShopSavvy Barcode Scanner app all goes fine. Also installing apps by putting apk's in my download folder via laptop seems to work fine.
Before this problem occured I fiddled around with the format tool AParted for my external sd, and the link2sd app. I deleted both of them, but the problem is still occuring.
Any help on this issue?
Here a catlog screen of the errors occurring when i install root browser. Similar error on youtube install.

[Completed] Insufficient Storage issue of Google Play Store

Hi guys. I am starting a new thread for this issue, because I have practically tried every possible options to solve the Insufficient storage issue, with no result! Sometimes an app doesn't start downloading, the error box opens showing " There is insufficient space in your internal storage and SD card, please free up some space...." Some other times, the app downloads fully, but can't be installed as the error box appears again - "Insufficient storage."
My device is Lenovo A6000, it's just a few months old. I have more than 500MB in my internal storage and a little less than 6GB on my external SD. I am running Android ver 4.4.4 and have my Play Store updated to the latest version since it automatically updates itself.
I have tried these ways:-
1. Deleting Cache.
2. I uninstalled the updates to Play store to revert it back to the factory version. It worked well for some time, then again the same issue.
3. I unmounted the SD card and remounted it again.
If I transfer an app from another device via ShareIt, I can install it perfectly!
I don't want to root my device just as yet. I mean, isn't there any good way to solve this issue? Is factory resetting the only option here?:crying::crying:
Thanks in advance for any help you guys can give.
Hi,
Try posting your question here:
http://forum.xda-developers.com/t/lenovo-a6000
The experts there may be able to help.
Good luck!

[Fixed]Need some help

Alright, I've tried everything I could, looked online(/in the forums) for solutions or help, but I just can't figure this out... After struggling a great deal installing the 5.2 update on my K1, I decided to simply flash the 5.2 recovery os image and start from there.
That went fine, so I went to install Magisk to root my tablet, but that didn't go as well. I ran into the same issue I was running into trying to update to 5.2 which is that my storage doesn't properly mount in TWRP (it works normally when using a file manager on the tablet itself and gets detected as it should by the storage manager in settings). I formatted the SD-card I'm using as partially Internal/adaptable storage and partially external, which is probably what causes the problem as TWRP shows the external SD card perfectly, but of the internal storage it only shows the contents of a folder named "InternalStorage' (presumable /sdcard/internal storage, however I can't actually see this to confirm) which is present on the root of the internal SD card. Any files that are in for example my Downloads folder on the internal storage aren't shown in TWRP. I thought installing a factory image would fix this issue, but it hasn't.
In either case, to get around this issue I sideloaded the Magisk zip file to root and it wen't as expected, didn't get any errors. But after booting my tablet, the Magisk Manager app wouldn't finish loading, it's stuck on the flash screen with the Magisk logo. Used the uninstaller and reinstalled through TWRP by placing the zip files on the external SD card and the app still won't load properly. I figure it has something to do with the way I have my SD card setup/partitioned, but I'm at my wits end as to how to fix this atm...
Any help will be appreciated! Preferably something that doesn't include re-partitioning the SD card :angel:
PS: The tablet was rooted with SuperSU before the factory reset, but I'm wanting to make the switch to Magisk because I want to install the Sony Framework to use Remote Play. If there is any other way to install the Sony Framework, using Xposed for example, I can maybe try rooting with SuperSU again.
EDIT: I fixed the issue, turned out the app was installed on the external sd card, moved it to internal storage and it worked!

How can I definitely check whether or not rooted S7 is encrypted

Hey people,
I'm getting mixed signals from my phone on whether it is encrypted or not and I would like to know how to find that out for sure.
My goal is to have a stock rom android 8 on my S7, rooted, with encryption.
I recently flashed the latest stock oreo build with odin, I don't remember if I let it boot once before the next step, but I think I did (I read the following thread only after I did this: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007)
Then, I installed TWRP via odin, booted into TWRP, formated /data, copied the magisk v16.0 installer zip to the now mounted /data and installed it.
Next, I booted the phone and set up all my accounts and apps.
Finally, I looked into how to get Samsung Health running on the rooted phone and manually set the ro.config.tima property in build.prop to 0 (and I still have no trouble restarting the phone).
The result is, that the phone is rooted, TWRP can not mount /data anymore (which seems to be a hint that the phone is encrypted), but in the android settings, I still have the option to encrypt the device (right above the option to encrypt the sd card) and changing the tima property did not cause any trouble, which again seems to be a hint the phone is not encrypted.
Does anyone know how to check if the phone is now encrypted or not?
If /data can be mounted in TWRP, you aren't encrypted. I'm trying to do the same thing only in an S8, with no luck getting encryption working. If I try to encrypt using settings, the phone reboots after a few minutes on the encrypting splash screen without encrypting anything. It worked fine on an S7 with Nougat stock.
danielwbn said:
Hey people,
I'm getting mixed signals from my phone on whether it is encrypted or not and I would like to know how to find that out for sure.
My goal is to have a stock rom android 8 on my S7, rooted, with encryption.
I recently flashed the latest stock oreo build with odin, I don't remember if I let it boot once before the next step, but I think I did (I read the following thread only after I did this: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007)
Then, I installed TWRP via odin, booted into TWRP, formated /data, copied the magisk v16.0 installer zip to the now mounted /data and installed it.
Next, I booted the phone and set up all my accounts and apps.
Finally, I looked into how to get Samsung Health running on the rooted phone and manually set the ro.config.tima property in build.prop to 0 (and I still have no trouble restarting the phone).
The result is, that the phone is rooted, TWRP can not mount /data anymore (which seems to be a hint that the phone is encrypted), but in the android settings, I still have the option to encrypt the device (right above the option to encrypt the sd card) and changing the tima property did not cause any trouble, which again seems to be a hint the phone is not encrypted.
Does anyone know how to check if the phone is now encrypted or not?
Click to expand...
Click to collapse
First thing first. When following old guides, sometimes they still work, often a security patch has closed the loop. So it is always preferable you look for a guide which specifically mentions OREO and the firmware versions your using.
Secondly, flash latest stock Oreo for your region (preferably unbranded) then root via any Oreo root guide on the forum and job done. Phone on stock, rooted and encrypted. Encryption is enabled by default on INTERNAL storage of stock ROM, rooting or TWRP doesn't change that. SD card remains open until you encrypt.
TWRP reporting internal storage at 0mb because it's encrypted yay!

Can't update SD-Card Apps Android 8.0

Hi,
I can't update apps moved to SD Card on my Android 8 Device via Playstore.
Download always fails going over 100%, tried 3 times then canceled.
Have to move to internal to update.
I once cleared app data of play store / services, may be related, not sure.
Any ideas?

Categories

Resources