Hello,
First off, sorry if I make any english mistakes as it's not my native language.
I'm running into some issues with my Stratos 3. It was running fine until now, stock firmware and nothing modified since I got it. The first issue was during the OTA update (4.2.5.0) which didn't completed. Just the /!\ sign at the end and the watch rebooted to normal.
It could just end there but I just wanted to update and followed the Gearbest "solutions" to update failures which seemed to be logical at first ... "Sign out of Amazfit App and log in again. When you open Amazfit app, app will connect with watch and update automatically." That's what I did, and the problems started ... Now the watch is stuck in some kind of bug, the screen keeps displaying this. Whatever I do, the watch come back to this error. I can't access any menu.
Photo :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what I already tried :
- Reboot the watch => same
- Installed ADB drivers, plugged it then factory reset (adb reboot wipe) => same
- If I just reboot it in MCU mode (adb reboot MCU), the watch works fine but it seems there isn't anything more I can do in it.
What I'm considering at this point is just doing a clean install (I was reading the stock firmware topic : https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-global-international-t4031153 ), but I'm not sure if it's the right direction. Just wanted to get some insight before doing something wrong.
Thank you very much for your help.
I continued digging into this issue. Found out it is a "common" error on Android systems (Hamazfit OS is based on Android).
What is pointed on most topics is a permission issue. Seems like when permissions are fixed, the problem is solved.
If this is the right direction to follow, the question remains on how to adapt it for this OS as the packages and the permissions may be different.
The main topic I found was on android.stackexchange (can't link with a new account for now).
Interesting part here :
I noticed when clicking report that the issue was a permissions issue.
using adb shell dumpsys package com.google.android.setupwizard you will see two lists related to permissions, one requested permissions, and one install permissions.
Comparing these lists, there were 8 items requested, but not installed. I fixed this using:
pm grant com.google.android.setupwizard android.permission.CALL_PHONE
pm grant com.google.android.setupwizard android.permission.GET_ACCOUNTS
pm grant com.google.android.setupwizard android.permission.PROCESS_OUTGOING_CALLS
pm grant com.google.android.setupwizard android.permission.READ_CONTACTS
pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
pm grant com.google.android.setupwizard android.permission.WRITE_CONTACTS
pm grant com.google.android.setupwizard android.permission.READ_OWNER_DATA
pm grant com.google.android.setupwizard android.permission.WRITE_OWNER_DATA
Note that the last two items gave an error message: Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permission.READ_OWNER_DATA. But ignoring those, now my phone worked again.
I'm no expert in this, I'll take any advices or recommendations.
EDIT : Just did the dumpsys on the watch. There is only the "grantedPermissions" at the end. No list of RequestedPermissions ...
C:\adb>adb shell dumpsys package com.huami.watch.setupwizard
Activity Resolver Table:
Non-Data Actions:
android.intent.action.MAIN:
6b57ee6 com.huami.watch.setupwizard/.InitialLanguageActivity
Key Set Manager:
[com.huami.watch.setupwizard]
Signing KeySets: 1
Packages:
Package [com.huami.watch.setupwizard] (33d54c27):
userId=10023 gids=[3002, 3001]
pkg=Package{3afe11f8 com.huami.watch.setupwizard}
codePath=/system/app/SetupWizard
resourcePath=/system/app/SetupWizard
legacyNativeLibraryDir=/system/app/SetupWizard/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=22 targetSdk=23
versionName=5.1-55
splits=[base]
applicationInfo=ApplicationInfo{1c2f7ed4 com.huami.watch.setupwizard}
flags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
dataDir=/data/data/com.huami.watch.setupwizard
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
timeStamp=2020-01-25 01:55:45
firstInstallTime=2020-01-25 01:55:45
lastUpdateTime=2020-01-25 01:55:45
signatures=PackageSignatures{24d5c87d [1fcaa372]}
permissionsFixed=false haveGids=true installStatus=1
pkgFlags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
User 0: installed=true hidden=false stopped=false notLaunched=false enabled=0
grantedPermissions:
android.permission.WRITE_SETTINGS
com.huami.watch.permission.READ_USER_SETTINGS
com.huami.watch.permission.WRITE_USER_SETTINGS
android.permission.DEVICE_POWER
android.permission.BLUETOOTH
android.permission.BLUETOOTH_ADMIN
android.permission.WRITE_SECURE_SETTINGS
android.permission.CHANGE_CONFIGURATION
android.permission.VIBRATE
android.permission.WAKE_LOCK
Litle update here, in case some people end here :
After some days, I asked to the seller (Amazfit Official Store on Aliexpress) for support. We talked a bit about the issue but we obviously couldn't find a solution. They offered me to send back the watch and replace it.
I was going to send it back until I checked the price for my local post office to send it in Hong Kong (about 55€/60$ for this tiny package ... ). So I deciced to take the risk and proceed to flash the watch myself.
First, unlocked the bootloader then followed the post for the stock FW installer (https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-global-international-t4031153)
And ... It worked ! :good: Now my watch is working correctly. I could link it to my phone again and my data were saved locally on my phone, so I didn't lose that either.
So I may have lost my warantly but at least, now I know how expensive this would be
In any case, I don't think I could do anything else after all the search I did.
What firmware version are you using to fix the problem?
Related
Pre-question summary: I had an eris for about a year. Trackball took a ****, got a refurb at verizon yesterday and like a big idiot didn't even check to make sure the microphone worked before rooting? (how dumb am I?)
so here I am, on a rooted refurb with just the "eris21official-root.zip" running (not the leak)
1) I tried running the ruu but got the error 140 / bootloader version error
- ok , so I found that I need to follow jcase's flash any ruu steps here:
http://forum.xda-developers.com/showthread.php?t=726885&highlight=unroot
2) I get stuck like everyone else at point cmd promt 4 which attempts to flash the misc.img to the phone, I get a not found error, wtf!!!!! Am I supposed to be unzipping this misc.img.zip file or leaving as is? I feel like I have tried everything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) I just tried running the last PB00IMG.zip (v3) through bootloader and got the error stating my current getup is newer than what I'm trying to 'update' it with
***my bootloader = HBOOT-1.49.0000
***error = Main Version is Older! Update Fail!
please help me
anybody
for the record here is my current tools directory:
Ruu epic fail
last thing, I am using the ruu from shipped-roms website
"RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with
_driver.exe"
it's showing up as 124 mb
http://shipped-roms.com/shipped/Desire/RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe
Chicago Ben said:
2) I get stuck like everyone else at point cmd promt 4 which attempts to flash the misc.img to the phone, I get a not found error, wtf!!!!! Am I supposed to be unzipping this misc.img.zip file or leaving as is? I feel like I have tried everything
Click to expand...
Click to collapse
Try reading the post a little further - jcase had a typo in his instructions which he never fixed. It was subsequently corrected in post # (lucky) 13
the original typo was
Code:
adb shell /data/local/flash_image misc misc.img
which should have been
Code:
adb shell /data/local/flash_image misc /data/local/misc.img
As to the question about "img.zip" versus ".img", the answer is obvious from looking at the (now corrected) instructions - you push "misc.img" to /data/local/misc.img, not misc.img.zip to /data/local/misc.img.zip
bftb0
[ Edit ] PS: I just looked through that post ("HowTo: Flash Any Ruu")
What a friggen comedy of errors!
Poster #1 gives some almost correct instructions
Poster #13 tries to correct the fault in instructions given in #1, and in so doing, introduces a new mistake in the same line he corrected
Posters thereafter repeat different variations of #1 or #13 variously claiming $hit like "you need to keep trying it until it works".
LOL.
The correction that I gave above to line #4 should work. When you do an "adb shell" the current directory of the shell is "/", and
- "flash_image" is not in the shell's $PATH
- misc.img is not stored at /misc.img - it is not in the current directory (namely, "/")
So, you need to explicitly give the full path to both the program you are trying to execute ("flash_image"), as well as the full path of the file that program is supposed to read ("misc.img"), as in:
adb shell /data/local/flash_image misc /data/local/misc.img
.
Thank you for the reply but I'm still struggling hard here. It didn't work. Here is a new snapshot of my local tools directory. You can see I have the zip and the uncompressed .img files there just to make sure
****...
I got somewhere ....
I was now looking at jcase's "How To Install Engineering bootloader FOR LEAK ROOTERS"
and downloaded the custom.img
http://forum.xda-developers.com/showthread.php?t=725047
flashed engtools3.zip
rebooted in bootloader and it got past the error I was receiving before about the current version being newer
Wow. It worked. So I followed steps 2, 3, 4 (used v3 (most recent) PB00IMG), 5 the "flashed engtools3.zip code"
rebooted holding vol down (bootloader) then BLAMO
going back to verizon tomorrow to show them I have a faulty refurb that I haven't even rooted
Haha yeah I don't proof read. My bad. Glad my old work is still sorta useful.
REALLY glad bftb0 is here cleaning up my mistakes.
thx broham
I recently upgraded my HTC incredible from CM 7.1 to AOKP. Ever since the upgrade I cannot install any of my APKs from Eclipse or ADB. In Eclipse I get the error:
[2012-02-20 16:17:40 - ABC] Android Launch!
[2012-02-20 16:17:40 - ABC] adb is running normally.
[2012-02-20 16:17:40 - ABC] Performing com.vorsk.ABC.ABCActivity activity launch
[2012-02-20 16:17:40 - ABC] Automatic Target Mode: using device 'HT06YHJ01492'
[2012-02-20 16:17:40 - ABC] Uploading ABC.apk onto device 'HT06YHJ01492'
[2012-02-20 16:17:40 - ABC] Installing ABC.apk...
[2012-02-20 16:17:41 - ABC] Installation failed due to invalid URI!
[2012-02-20 16:17:41 - ABC] Please check logcat output for more details.
[2012-02-20 16:17:41 - ABC] Launch canceled!
In ADB I get:
C:\Users\lanrat\workspace\ABC\bin>adb install ABC.apk
1044 KB/s (23523 bytes in 0.022s)
pkg: /data/local/tmp/ABK.apk
Failure [INSTALL_FAILED_INVALID_URI]
Any ideas on why this is happening? If I move the apk to my SD card first it installs just fine.
I really don't want to go back to CS 7.1 just to get the ability to develop apps back
Had this problem on the Incredible as well. As a new user I can't post links, but there's a StackOverflow post that details the fix. First Google hit for INSTALL_FAILED_INVALID_URI.
Basically /data/local doesn't have the right permissions, so a simple
Code:
adb shell
cd /data
chmod 777 local
should fix you up. Not sure if the new permissions are overbroad, but I'm not too worried.
That fixed it.
I tried chmod 777 /data/local/tmp but that did not work.
I wonder what caused this issue in the first case, its relatively fresh install of the rom.
JokoInteractive said:
Had this problem on the Incredible as well. As a new user I can't post links, but there's a StackOverflow post that details the fix. First Google hit for INSTALL_FAILED_INVALID_URI.
Basically /data/local doesn't have the right permissions, so a simple
Code:
adb shell
cd /data
chmod 777 local
should fix you up. Not sure if the new permissions are overbroad, but I'm not too worried.
Click to expand...
Click to collapse
Thanks, this helped.
I had to chmod 777 both /data and /data/local on ics rom for htc incredible. This really surprised me.
Same thing happened to me since I upgraded my phone to Jelly bean.
I'm on SGS 3 (I9300) with freshly installed I9300XXDLIH_I9300VFGDLJ1_VIP and rooted afterwards.
Eclipse still displays this:
Installation failed due to invalid APK file!
Please check logcat output for more details.
Launch canceled!
Click to expand...
Click to collapse
Even though I have done: chmod 777 /data /data/local /data/local/tmp
Code:
[email protected]:/ # ls -ld data data/local data/local/tmp
ls -ld data data/local data/local/tmp
drwxrwxrwx system system 2012-10-23 15:40 data
drwxrwxrwx root root 2012-08-25 10:40 local
drwxrwxrwx shell shell 2012-10-23 16:36 tmp
Eclipse still refuses to install (any) APK.
If I copy the Eclipse-generated APK to the phone, I can install it manually.
What can I do to fix this?
FYI, I've the the 20.0.3 Android SDK on fully updated Eclipse 4.2.1
My system properties:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update:
Installed SiyahKernel S3-v1.6.8 and w/o any tampering with the settings (e.g. through ExTweak) the problem is solved.
Root cause seems to be UMASK.
- on stock kernel I had 0077
- now on SiyahKernel I have 0000
Still, as can be seen from numerous other threads on the same issue out there, it's very wrong for the stock kernel to cause that problem.
Hello everyone,
I spent a couple of hours searching on the forum before asking this question. Maybe I am not searching the right thing but I just received a new company phone. It is a Samsung Galaxy S10e. My previous one was an S7.
The company has this Intelligent Hub app installed with admin rights that doesn't allow me to turn off the location services. It drains the battery fast when the services are enabled especially that most of my work is being done in a weak signal or no signal area. (Placing the phone in airplane mode doesn't work since it's admin controlled.
I tried to uninstall the app via adb but I get this DELETE_FAILED_DEVICE_POLICY_MANAGER. The package name is com.airwatch.androidagent
Can anyone please let me know if there's a way to uninstall this package by bypassing the admin rights?
Thank you!
what command you use on ADB to uninstall it
ineedroot69 said:
what command you use on ADB to uninstall it
Click to expand...
Click to collapse
pm uninstall -k --user 0 'com.airwatch.androidagent'
google say you're receiving DELETE_FAILED_DEVICE_POLICY_MANAGER because the application you are tying to uninstall is a "device manager application" . device manager are application that helps you locate, and if needed, remotely lock or wipe your Android device if stolen so you just need to remove ”Intelligent Hub" being a device manager usually that can easily be change by going on phone settings
ineedroot69 said:
google say you're receiving DELETE_FAILED_DEVICE_POLICY_MANAGER because the application you are tying to uninstall is a "device manager application" . device manager are application that helps you locate, and if needed, remotely lock or wipe your Android device if stolen so you just need to remove ”Intelligent Hub" being a device manager usually that can easily be change by going on phone settings
Click to expand...
Click to collapse
Yes, but the problem is that it is control by an admin. I do not have rights to deactivate, force stop, uninstall. Those buttons are grayed out for me
How do I revoke admin to an app via dm command
what do you means grayed out? just go to Setting and find "Device Manager/Administrator" (you can find it by typing it on Setting searchbar or manually looking for it) and just uncheck Intelligent Hub on it
I am trying to figure this out also. I have a company phone that IT is the ADMIN on Pixel5. I tried to uninstall the
I tried to uninstall the app via adb com.airwatch.androidagent but get this error DELETE_FAILED_DEVICE_POLICY_MANAGER.
I have same problem. Even as su I get for
pm uninstall -k --user 0 com.samsung.android.kgclient
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
If I look into settings/app/special access/device administrative apps (maybe mistranslated) - there is just my NOVA Launcher listed.
What the hell is the policy manager?
starbright_ said:
I have same problem. Even as su I get for
pm uninstall -k --user 0 com.samsung.android.kgclient
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
If I look into settings/app/special access/device administrative apps ((maybe mistranslated) - there is just my NOVA Launcher listed.
Click to expand...
Click to collapse
i disable my launcher as device administrator... Xiaomi launcher is great but i don't trust it as Device Administrator it my sell my info to China
look it don't even have description it just say "Launcher"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, what I want to tell is that I don't know what Policy Manager is (who let me fail uninstalling that package), and that there is no app is a device manager. Sorry for confusion.
I didn't allow Nova Launcher to be Admin. And this is the only left app in the list. But this becomes OT here
-
Having this error DELETE FAILED OWNER BLOCKED? if its tied to the Samsung knox deployment. how to remove it?
DISCLAIMER: This guide works on any phone with Android 11 or newer. Previous versions do not have wireless debugging so this is not possible.
Hey all! In this short guide, I will be showing you how to give any app the permission "WRITE_SECURE_SETTINGS" without needing to connect to a computer.
For this guide, I will be using System UI Tuner by Zachary Wander as my example app.
First, download and install Shizuku. This is a wonderful app that allows system API access directly without needing to root your phone.
Once you've installed Shizuku, follow the steps to start it through the wireless debugging method. You will only need to pair once as long as you don't reinstall the app.
DISCLAIMER: Shizuku will need to be restarted if you restart your phone but it's just a matter of re-enabling wireless debugging and then clicking "Start" in the Shizuku app.
Next, we're going to install Termux by Fredrik Fornwall. Simply open the app once, wait for it to finish installing, then leave the app.
Now, re-enter Shizuku, and click the button that says "Use Shizuku in terminal apps".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then click "Export files".
Afterwards, make a new folder, and call it "Shizuku".
Finally, click "Use this folder".
Almost there!
Head over to Termux, and type:
Code:
pkg install nano
This installs a text editor that we will use to edit our Shizuku config file.
While it's installing, go to Termux's app info, and change the permissions to allow it access to all files. This will allow it to see the folder we made earlier.
Go back to Termux, and after nano is done installing, type the following:
Code:
cd /sdcard/Shizuku
nano shizuku
Once inside the text editor, press the CTRL key on Termux's key bar, and press the "\" key on your keyboard.
Now, type "PKG", press Enter, then in the next field, type "com.termux".
Now, tap "a", tap Ctrl+X, tap "y", and you're done!
Whenever you want to authorize an app with "WRITE_SECURE_SETTINGS" simply open Termux, cd to "/sdcard/Shizuku", and type:
Code:
sh shizuku pm grant <package name here> android.permission.WRITE_SECURE_SETTINGS
You will only have to do this once per app as long as you do not uninstall it.
Have fun!
So this broke my brain just a bit (it's been one of those days) however if I am reading it correctly this will give some apps a pseudo root.
alarmdude9 said:
So this broke my brain just a bit (it's been one of those days) however if I am reading it correctly this will give some apps a pseudo root.
Click to expand...
Click to collapse
Sort of, it's the highest permission you can give an app without rooting your phone.
Does it allow you to say debloat the phone or things like that?
alarmdude9 said:
Does it allow you to say debloat the phone or things like that?
Click to expand...
Click to collapse
I'm not sure I haven't tested it that far but you can access all app data folders with it so maybe?
alarmdude9 said:
Does it allow you to say debloat the phone or things like that?
Click to expand...
Click to collapse
I'm not sure I haven't tested it that far but you can access all app data folders
Hmmm have to get some time to try this. Adulting sucks.
Hello, so I'm stuck on the /sdcard/
I dont have one is just on internal storage Shizuku folder... How do im supposed to type it
Does Shizuku still work with the N200 after the November update?
I was able to get everything setup to the last step where I grant packages write permissions, but every package I name returns 'pm: no such file or directory'.
If I use Termux to try to navigate to /SD card/Android/data i get 'cannot open directory: permission denied'. I'm wondering if Termux can even access the apps to give them elevated permissions?
Finnzz said:
Does Shizuku still work with the N200 after the November update?
I was able to get everything setup to the last step where I grant packages write permissions, but every package I name returns 'pm: no such file or directory'.
If I use Termux to try to navigate to /SD card/Android/data i get 'cannot open directory: permission denied'. I'm wondering if Termux can even access the apps to give them elevated permissions?
Click to expand...
Click to collapse
I have same error
Hello friends
I uninstalled the com.android.documentsui package with adb a few days ago
And I really got into trouble
How can I reinstall it?
I have to say that I found the apk file on the Internet, but when I use
Code:
pm install --user 0 android.documentsui-7.0.apk
, I get this error:
Code:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.android.documentsui signatures do not match the previously installed version; ignoring!]
Can anyone help me? Or say goodbye to document?
ciger7 said:
Can anyone help me? Or say goodbye to document?
Click to expand...
Click to collapse
I'm not an expert so I don't know if this will help, but Occam's Razor says that you can switch OUT of adb to install & uninstall, and then, after you get out of this locked-up situation, you can try adb again later.
You didn't mention so I need to ask a basic debugging question:
QUESTION:
Did you try to uninstall directly from the phone (without using adb) and then try to install directly on the phone (again, without adb)?
If so, do you get any errors and if so, are they the same or different than what you get using adb?
GalaxyA325G said:
I'm not an expert so I don't know if this will help, but Occam's Razor says that you can switch OUT of adb to install & uninstall, and then, after you get out of this locked-up situation, you can try adb again later.
You didn't mention so I need to ask a basic debugging question:
QUESTION:
Did you try to uninstall directly from the phone (without using adb) and then try to install directly on the phone (again, without adb)?
If so, do you get any errors and if so, are they the same or different than what you get using adb?
Click to expand...
Click to collapse
In answer to your question:
Document software is a system software and can not be deleted or disabled by the user. I deleted it with adb.
In response to your second question:
I could not install it normally and with the phone and encountered this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since I completely deleted this program from the device, I do not understand the reason for this error!
ciger7 said:
Hello friends
I uninstalled the com.android.documentsui package with adb a few days ago
And I really got into trouble
How can I reinstall it?
I have to say that I found the apk file on the Internet, but when I use
Code:
pm install --user 0 android.documentsui-7.0.apk
, I get this error:
Code:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.android.documentsui signatures do not match the previously installed version; ignoring!]
Can anyone help me? Or say goodbye to document?
Click to expand...
Click to collapse
When you uninstall any sys app from adb, still apk will be there.
I guess you may have use adb command like
Code:
pm uninstall --user 0 package.name
In that case simply do this
Code:
pm install --user 0 package.name
replace package name with one you want.
In case you have used command hide instead of uninstall, use
Code:
pm unhide --user 0 package.name
Thanks, I will try this
Make your solution look right
But I think in order for the apk file to remain, I have to use -k (keep data), which I did not use. It is true?
dr.ketan said:
When you uninstall any sys app from adb, still apk will be there.
I guess you may have use adb command like
Code:
pm uninstall --user 0 package.name
In that case simply do this
Code:
pm install --user 0 package.name
replace package name with one you want.
In case you have used command hide instead of uninstall, use
Code:
pm unhide --user 0 package.name
Click to expand...
Click to collapse
I tested your code and wrote:
Code:
pm install --user 0 com.android.documentsui
And I got this error:
Code:
Error: failed to write; com.android.documentsui (No such file or directory)
I can not understand what is the problem!
Do you know how to solve it?