root access – Problem reinstalling system app (Media Manager)

So at first my intention was to fix some other problem with DownloadManager but it ended messing up MediaManager which was crashing in loop. I reinstalled it and at first it was reinstalling fine but after a while I couldnt reinstall anymore. Heres the console output:

ASUS_X008_1:/system/priv-app/MediaProvider #
pm install MediaProvider.apk
Failure [INSTALL_FAILED_INVALID_APK: Package couldn't be installed in /data/app/com.android.providers.media-1: Package /data/app/com.android.providers.media-1/base.apk code is missing]

Its complaining for some reason about not having files in /data/app? Maybe it deleted some directions for system as to where its supposed to install system apps like this? Also if it helps my phone is Asus ZC520TL. I pulled media manager apk from stock firmware image but that didnt change anything.

Complete uninstall of ubuntu 18.04 before reinstalling 20.04

I’ve run into some issues on Ubuntu 18.04 dual-boot when trying to install some gpu drivers and I wanted to get a clean reinstall of Ubuntu 20.04. I formated the partitions on which Ubuntu was installed via diskmgmt.msc on Windows 10 but ubuntu still appears in the boot menu and i get into GNU Grub bash-like terminal when trying to boot into it. How to completely wipe Ubuntu 18.04 before installing the newest version ?

Trouble reinstalling v.20.04

My question is about REINSTALL ubuntu 20.04: I lost folders and/or dpkg files, then I cannot install programs or update. I have Ubuntu 20.04, and I am trying to REINSTALL ubuntu 20.04 cos i want not to lose my data (note: I have no dual boot and not microsoft OS). I have a gpt system and an efi partition with booting, but the reinstall tells me
"No EFI partition was found. This system will likely not be able to boot successfully, and the installation process may fail. Please go back and add an EFI system partition or continue at your own risk. "
NOTE: I want not format and istall again, even though I backed up my personal files.

$ sudo parted -l
(sudo) password for (user):
Model: ATA HGST HTS545050A7 (scsi)
Disk / dev / sda: 500GB
Sector size (logical / physical): 512B / 4096B
Partition table: gpt
Disc indicators:

Number ……Start …….End ………Size …….. File system ….Name Flags
1……………..1049kB …538MB … 537MB ….fat32 …………..EFI System Partition boot, esp
2 …………….538MB …500GB ….500GB …..ext4

QUESTION: Should I continue or what ?. THANKS!

applications – GALAXY TAB 2 ANDROID 4.0.3. problem reinstalling BorrowBox Library app

I bought the above in April 2017 mainly to use it as an ebook reader for public library services.

I installed Overdrive and BorrowBox, and both have worked fine till now.

However on a recent attempt to use BorrowBox, it ‘jammed’ on an opening screen. Closing down and restarting failed to shift this, and I uninstalled the app, thinking to reinstall it, and get it
working again.

Needless to say, there was no reistall option; and an attempt to reload it from playbox failed with the ‘incompatible’ message.

Bolinda of course does not support or provide earlier versions. The only source I can find on the web has
versions back to 2.9.14, but that requires android 4.1.

I found a reference and download link to V2.7.0, compatible with android 4.0, but the link no longer works.

How can I get back to a usable Borrowbox application, without having to replace an otherwise working tablet?

Have I deleted the code when I uninstalled ? I can find nothing searching the file directory which suggests it might still be there.

Can anyone provide a copy of BorrowBox v2.7.0 or earlier, or point me at a source ?

Hoping someone can point me in the right direction.

How can I find photos in Lightroom Android app after reinstalling it?

I uninstalled my Light room application in Android and after reinstalling it and logged in my account all my 300 photos disappeared. Is there any way to explain how did this happen and how can I take back my photos?

9.0 pie – Google Chrome and picture reenabling and reinstalling without authorization or interaction?

As somebody really wary of Google in general, the first thing I did on my phone was to disable Chrome and Google Pictures, and replaced them by apps from F-Droid

For a few days now, I’ve seen them reappear in my app drawer, and with careful observation, the play store seems to be re-enabling and reinstalling them by itself when checking if updates are available.

Uninstalling and disabling them again just kick the can down to the next repository upgrade.

This question talk about google chrome, but do not give an explanation for google pictures.

Auto updates are disabled, android 9.

installation – How do I revoke permissions that are preventing an App reinstalling on Android Pie

I am trying to re-install File Commander in Android 9 but Office Suite is creating a conflict with the permissions. I tried uninstalling Office Suite but no change. File Commander isn’t installed.

This is the error I am getting:

D:ADB>adb install File_Commander-Premium-v6.6.34940.apk adb: failed to install File_Commander-Premium-v6.6.34940.apk:
Failure (INSTALL_FAILED_DUPLICATE_PERMISSION:
Package com.mobisystems.fileman attempting to redeclare permission com.mobisystems.CustomReadWritePermission already owned by com.mobisystems.editor.office_registered)

Here are the permissions:

G8441:/ $ pm list permissions | grep com.mobisystems
permission:com.mobisystems.CustomReadWritePermission
permission:com.mobisystems.editor.office_registered.licenses

I tried several syntax with the revoke command but I am getting errors:

D:ADB>adb shell pm revoke com.mobisystems permission.com.mobisystems.CustomReadWritePermission

Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown package: com.mobisystems
        at com.android.server.pm.permission.PermissionManagerService.revokeRuntimePermission(PermissionManagerService.java:1515)
        at com.android.server.pm.permission.PermissionManagerService.access$1200(PermissionManagerService.java:89)
        at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.revokeRuntimePermission(PermissionManagerService.java:2112)
        at com.android.server.pm.PackageManagerService.revokeRuntimePermission(PackageManagerService.java:5539)
        at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1732)
        at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:219)
        at android.os.ShellCommand.exec(ShellCommand.java:103)
        at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21524)
        at android.os.Binder.shellCommand(Binder.java:634)
        at android.os.Binder.onTransact(Binder.java:532)
        at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2796)
        at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3978)
        at android.os.Binder.execTransact(Binder.java:731)

D:ADB>adb shell pm revoke com.mobisystems com.mobisystems.permission.com.mobisystems.CustomReadWritePermission

Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown package: com.mobisystems
        at com.android.server.pm.permission.PermissionManagerService.revokeRuntimePermission(PermissionManagerService.java:1515)
        at com.android.server.pm.permission.PermissionManagerService.access$1200(PermissionManagerService.java:89)
        at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.revokeRuntimePermission(PermissionManagerService.java:2112)
        at com.android.server.pm.PackageManagerService.revokeRuntimePermission(PackageManagerService.java:5539)
        at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1732)
        at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:219)
        at android.os.ShellCommand.exec(ShellCommand.java:103)
        at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21524)
        at android.os.Binder.shellCommand(Binder.java:634)
        at android.os.Binder.onTransact(Binder.java:532)
        at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2796)
        at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3978)
        at android.os.Binder.execTransact(Binder.java:731)

Can anyone expert in ADB please tell me the right command or syntax to revoke these permissions or to fix this issue?

Thanks in advance

printing: printer does not print after reinstalling ubuntu 20.04 Part A

First, be patient with me since I'm new to ubuntu. I had Ubuntu 19.10 installed on my computer and my printer didn't work. I upgraded to 20.04 and still had no problems until I had to reinstall 20.04. In the first install startup directory it was all one, now I have switched to startup on a separate partition (I don't think that's part of the problem, but & # 39; I'm trying to give you as much info as I can I went into ubuntu wiki "debugging print issues" and ran the terminal commands that were there, below is the output of my terminal session.

james @ asus-main: ~ $ lpstat -p -d
The Canon_MG5300_series printer is idle. enabled from Wed 06 May 2020 08:40:43 PM
no default system destination
james @ asus-main: ~ $ lpoptions -d printer
lpoptions: printer or class unknown.
james @ asus-main: ~ $ lsmod | grep usb
usblp 24 576 0
usb_storage 77824 2 uas, ums_realtek
usbhid 57344 0
hid 131072 2 usbhid, hid_generic
james @ asus-main: ~ $ tail -f / var / log / syslog
May 6 8:54:12 PM asus-main systemd (1): Starting PackageKit Daemon …
May 6 8:54:12 PM Asus-main PackageKit: start daemon
May 6 8:54:12 PM asus-main dbus-daemon (782): (system) Service successfully activated & # 39; org.freedesktop.PackageKit & # 39;
May 6 8:54:12 PM asus-main systemd (1): Started PackageKit Daemon.
May 6 8:54:12 PM asus-main PackageKit: resolve transaction / 29_cbcedcda from uid 1000 successfully completed after 356 ms
May 6 8:54:39 ​​PM asus-main PackageKit: resolve transaction / 30_caccbeda from uid 1000 successfully completed after 352 ms
May 6 8:55:53 PM Asus-main PackageKit: resolve transaction / 31_edddebed from uid 1000 successfully completed after 354 ms
May 6 8:55:53 PM asus-main PackageKit: uid 1000 get-details / 32_cbdbcbcd transaction completed successfully after 358 ms
May 6 8:57:35 PM asus-main snapd (798): api.go: 985: Installation of unmounted "libreoffice" hotfix
May 6 8:57:45 PM asus-main systemd (1727): gnome-launch-gnome-control-center.desktop-6086.scope: Succeeded.

For some reason, I couldn't post my entire question in one post because it kept telling me that my post looked like spam, it searched for solutions, suggested I get rid of the lint, I need the lint to make my point.

Crashes: Autopsy of Android 8 death in low memory and battery condition, manifesting as pattern crash, heals by reinstalling OS

The device in question is a Samsung J4, the model was released in May 2018, and the device was purchased and activated in early 2019.

The device comes with Android 8.0, consists of a standard ARM processor with 4 cores, its short-term memory is 2 GB wide and its buffer memory is 16 GB high, its long-term memory is cloud-based and is compatible with Google and Facebook and is used for its most important functions. services, slow communication with Gmail, fast communication with Whatsapp and Google Drive, and long-term storage of the camera with Google Photos.

The patient started coming to consultations in November last year, the symptoms described were insufficient space errors and the constant deletion of files assisted by the operating system, a MicroSD card was prescribed. But two months later, the patient returned again, the problems persisted. On inspection, the SD card remains unused, apparently the operating system lacked automatic support. Furthermore, it was impossible to manually configure additional storage for any application, so the patient received training on how to clean up their most important sources of disk space consumption, WhatsApp videos.

The patient arrived in critical condition today, the phone was still working, a WhatsApp call was active in the background, but the screen was locked and the usual pattern password was not working. After some attempts made by the owner, the screen was unlocked again. It was also observed that the battery was running low.

A few minutes after the incident, the phone locked again, this time the user was unable to unlock it, they tried unsuccessfully to remove the battery, tried to generate a "Forgot your password" alert, but there seemed to be no protection against the brutal forces, at User was allowed to try as many combinations as he wanted. Google Device Finder was used to lock the phone, but there was no option to remove the pattern. Ultimately, the best course of action was considered to be to erase persistent phone storage and reinstall its operating system.

The patient is now receiving therapy to reinstall all their old applications and settings. A phone backup was offered but declined to avoid reinstalling old problems and prioritizing disk space.

My prevailing theory is that low disk space and low battery conditions triggered a chain reaction of failures, at some point an error was triggered by a non-atomic write that was interrupted by a kernel initiated crash due to low memory or reduced processing power initiated by low battery, most likely a combination of these two.

The mechanism of action of such error possibly consisted of:

  • An overwrite of the pattern password.
  • An overwrite of any of the binaries involved in decrypting and unlocking the device. In this case, the error chain would have degraded the error message by restricting it to a narrow, state-based error reporting API presented by the pattern unlock screen.

Some researchers show that this is a common occurrence, however, it is not known if the cause of death is common, or if there is a singular manifestation of various causes of death.

The question here is, how did the system crash so fatally as to allow the operating system to be unrecoverable even after rebooting?

Ubuntu 18.04 booting into console mode even after reinstalling drivers

Basically I just did one thing (or an error I would say): apt-remove python2 and python3 since I wanted to reinstall it for other reasons. During the process, I think you can remove something "extra" and after rebooting I am stuck with ubuntu console mode.
I have already tried (more than once) to completely uninstall the nvidia drivers and reinstall them without success. I see they are there, but I am still in console mode. I've also checked the grub options during startup and don't see anything relevant other than splashing which should be harmless (that I know of).
Thank you in advance for your help.