I've upgraded my tablet from Cynogen to Lineage. When still on CM, I made a full adb backup. I used a tool to see what is in it, and it seemed all fine.
Now it's upgraded to Lineage. I did an adb restore, and it finished without errors or warnings. And the result: *nothing* got restored, not even after a reboot. Absolutely nothing.
What do I do to get the backup file restored?
adb logcat has entries for each and every app:
Code:
09-15 14:41:56.641 678 3422 I BackupManagerService: Package bz.ktk.bubble not installed; requiring apk in dataset
09-15 14:41:56.642 678 3422 D BackupManagerService: APK file; installing
09-15 14:41:56.642 678 3422 D BackupManagerService: Installing from backup: bz.ktk.bubble
09-15 14:41:56.686 2816 2828 W asset : Asset path /data/cache/backup_stage/bz.ktk.bubble is neither a directory nor file (type=0).
09-15 14:41:56.687 2816 2828 W DefContainer: Failed to parse package at /data/cache/backup_stage/bz.ktk.bubble: android.content.pm.PackageParser$PackageParserException: Failed to parse /data/cache/backup_stage/bz.ktk.bubble
09-15 14:41:56.689 678 3422 D BackupManagerService: [discarding file content]
How do I fix that??
Hi thany2
I had the exact same issue when trying to restore a backup made on Android 8.1 to Android 8.1.
Through trial and error, I found that `abe unpack` and `abe pack` fixes the issue and I was able to restore the backup. abe: android-backup-extractor. You might need to install apks beforehand. Just run `adb logcat` while restoring.
Related
I've had a problem ever since I've tried using 4.2 ROMs, such as CM10.1 and AOKP. I install the ROM, load my apps onto it, and when I reboot, not only does the reboot take a ridiculous amount of time (sometimes over 5 minutes) but some of the apps will have had their data wiped and some will just disappear completely!
Finding this really frustrating not being able to reboot without fear of losing apps and data, I decided to logcat the boot. The logcat is full of things like this:
Code:
W/PackageManager( 420): Package com.teslacoilsw.launcher at /system/app/com.teslacoilsw.launcher-1.apk reverting from /data/app/com.teslacoilsw.launcher-1.apk: new version 20003 better than installed 19504
W/PackageManager( 420): Package source /data/app/com.teslacoilsw.launcher-1.apk does not exist.
W/PackageManager( 420): Couldn't delete native library directory /data/app-lib/com.teslacoilsw.launcher-1
I/PackageManager( 420): Package com.teslacoilsw.launcher codePath changed from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk; Retaining data and using new
D/PackageManager( 420): No files in app dir /vendor/app
W/PackageManager( 420): Code path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Resource path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Permission com.android.launcher.permission.INSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
W/PackageManager( 420): Permission com.android.launcher.permission.UNINSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
That same error frequents throughout the boot, just with different package names for all the apps on my phone, both system and user apps. Here's a logcat of a boot.
At first I thought maybe it was because when I upgraded from 4.1 to 4.2 and restored my apps+data through TitaniumBackup that maybe the 4.1 data was screwing with something in 4.2, so I did a clean wipe of the ROM, downloaded the apps from the Play Store and didn't restore anything from TitaniumBackup, yet it was still doing it! I've tried wiping and reinstalling about 5 times now and I keep losing some apps+data on a reboot.
Can anyone who understands logcat a bit better than me or someone help me out?
dudeman1996 said:
I've had a problem ever since I've tried using 4.2 ROMs, such as CM10.1 and AOKP. I install the ROM, load my apps onto it, and when I reboot, not only does the reboot take a ridiculous amount of time (sometimes over 5 minutes) but some of the apps will have had their data wiped and some will just disappear completely!
Finding this really frustrating not being able to reboot without fear of losing apps and data, I decided to logcat the boot. The logcat is full of things like this:
Code:
W/PackageManager( 420): Package com.teslacoilsw.launcher at /system/app/com.teslacoilsw.launcher-1.apk reverting from /data/app/com.teslacoilsw.launcher-1.apk: new version 20003 better than installed 19504
W/PackageManager( 420): Package source /data/app/com.teslacoilsw.launcher-1.apk does not exist.
W/PackageManager( 420): Couldn't delete native library directory /data/app-lib/com.teslacoilsw.launcher-1
I/PackageManager( 420): Package com.teslacoilsw.launcher codePath changed from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk; Retaining data and using new
D/PackageManager( 420): No files in app dir /vendor/app
W/PackageManager( 420): Code path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Resource path for pkg : com.teslacoilsw.launcher changing from /data/app/com.teslacoilsw.launcher-1.apk to /system/app/com.teslacoilsw.launcher-1.apk
W/PackageManager( 420): Permission com.android.launcher.permission.INSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
W/PackageManager( 420): Permission com.android.launcher.permission.UNINSTALL_SHORTCUT from package com.teslacoilsw.launcher ignored: original from com.android.launcher
That same error frequents throughout the boot, just with different package names for all the apps on my phone, both system and user apps. Here's a logcat of a boot.
At first I thought maybe it was because when I upgraded from 4.1 to 4.2 and restored my apps+data through TitaniumBackup that maybe the 4.1 data was screwing with something in 4.2, so I did a clean wipe of the ROM, downloaded the apps from the Play Store and didn't restore anything from TitaniumBackup, yet it was still doing it! I've tried wiping and reinstalling about 5 times now and I keep losing some apps+data on a reboot.
Can anyone who understands logcat a bit better than me or someone help me out?
Click to expand...
Click to collapse
well...
only errors i see are:
Code:
E/Gmail.LabelManager( 2334): Unable to get label ^i for account [email protected]
E/Gmail ( 2334): Couldn't find label: ^i
are you using nova launcher? stable or beta? i was a user of nova launcher (switched to apex a few days ago) on CM; never seen such warnings.
my advice would be start fresh: flash stock images through fastboot, formatting the partitions before flashing them. update your bootloader to latest version if needed.
then flash latest twrp (can't suggest cwm version, but i assume latest non-touch would be the most stable, although some will say otherwise), and reflash your rom.
install fewer apps at the same time, rebooting in between.
Re: CM10.1 apps + data loss on reboot
bk201doesntexist said:
well...
only errors i see are:
Code:
E/Gmail.LabelManager( 2334): Unable to get label ^i for account [email protected]
E/Gmail ( 2334): Couldn't find label: ^i
are you using nova launcher? stable or beta? i was a user of nova launcher (switched to apex a few days ago) on CM; never seen such warnings.
my advice would be start fresh: flash stock images through fastboot, formatting the partitions before flashing them. update your bootloader to latest version if needed.
then flash latest twrp (can't suggest cwm version, but i assume latest non-touch would be the most stable, although some will say otherwise), and reflash your rom.
install fewer apps at the same time, rebooting in between.
Click to expand...
Click to collapse
Wait so the whole "couldn't delete data-lib" thing is normal..?
Yeah using nova, beta builds.
Hmm, okay I'll give flashing stock a try. How do I go about updating the bootloader? IIIRC I think there was a bootloader img in the stock folder, is it that?
Sent from my Galaxy Nexus using xda premium
Re: CM10.1 apps + data loss on reboot
dudeman1996 said:
Wait so the whole "couldn't delete data-lib" thing is normal..?
Yeah using nova, beta builds.
Hmm, okay I'll give flashing stock a try. How do I go about updating the bootloader? IIIRC I think there was a bootloader img in the stock folder, is it that?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes. Let us know how that turns out.
Sent from my i9250
Re: CM10.1 apps + data loss on reboot
bk201doesntexist said:
Yes. Let us know how that turns out.
Sent from my i9250
Click to expand...
Click to collapse
That seems to have worked. I didn't realise it would wipe my sdcard though, so I lost everything including over 10,000 texts :/ all I have is a TB backup from a week ago and my camera pics that dropbox auto uploaded. Oh well, can't do anything now, thanks a lot for your help
Sent from my Galaxy Nexus using xda premium
Hello i got a strange problem. Few days ago I got crash when i want to open (installed before and updated before to the last version) Dropbox. It happens suddenly. After update it works fine, but with next trying to open, apps got crash and closed. I decided to do reinstall, uninstalling and installing again, but i had some bugs/errors.
When i want to download i got problem called Error -24, i found sollution for it, but don't work for me.
Sollution is like:
Qewbicle said:
Go to
/data/data/
and search for your
com.application-address.whatever-it-may-be
Some of them you can tell what they are just by the names, the others, google-em.
If you wish to keep the information that it contains for the app, I recommend making a copy of it first.
Delete it
Install the application, it'll work, trust me.
Now replace it with your copy.
Done.
Click to expand...
Click to collapse
But it didn't works for me, after this i got problem with package lost in google play store. Sometimes i got LOW STORAGE info, but it is fake, cause i could install other apps, much bigger than dropbox - so i have space to install.
I delete folder com.dropbox from:
/data/data
/data/usr/0/
/data/system
every dropbox folder
I tried to install dropbox from official homepage, i get the app on my phone, but installation is not finish. I also tried to restore backup of Dropbox via titanium backup, but it stuck on the restoring (app only and same for app + data)
I don't have no idea what is wrong. I did also FIX APK Permission from 4EXT Recovery without any result.
Here is my logcat:
Code:
I/SystemServer( 418): DropBox Service
I/BootReceiver( 418): Copying /proc/last_kmsg to DropBox (SYSTEM_LAST_KMSG)
I/ActivityManager( 418): START u0 {act=android.intent.action.VIEW dat=file:///storage/sdcard0/Download/Dropbox.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 2538
I/AppSecurityPermissions( 2763): Ignoring unknown permission:com.dropbox.android.permission.C2D_MESSAGE
I/ActivityManager( 418): START u0 {dat=file:///storage/sdcard0/Download/Dropbox.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 2763
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
W/ActivityManager( 418): No content provider found for permission revoke: file:///storage/sdcard0/Download/Dropbox.apk
I/PackageManager( 418): Running dexopt on: com.dropbox.android
E/installd( 84): dexopt cannot open '/data/dalvik-cache/[email protected]@[email protected]' for output
W/PackageManager( 418): Package couldn't be installed in /data/app/com.dropbox.android-1.apk
I/InstallAppProgress( 2763): Finished installing com.dropbox.android
Any sollution? I am working with it about few hours... Thanks for help.
I almost forgot, after some restarts and clean dalvick-cache my Titanium Backup was gone, and i had to install it again, strange situation when app suddenly dissappear, any fix for it too?
Update:
I tried to install via terminal emulator but got message:
Code:
pkg: Dropbox.apk
Failure [INSTALL_FAILED_DEXOPT]
Oh well..
Upgraded from 10.0.4 to 10.0.6 via ota and boom my mobiledata is gone.
I do NOT want to factory reset. Lets try it if nothing else helps.
Can someone put somewhere where I can download files from 10.0.4 eu rom:
/system/priv-app/TeleService/*
My logcat shows:
FATAL EXCEPTION: main
Process: com.android.phone, PID: 10338
java.lang.RuntimeException: Unable to instantiate application com.android.phone.PhoneApp: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at android.app.LoadedApk.makeApplication(LoadedApk.java:1226)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6594)
at android.app.ActivityThread.access$1600(ActivityThread.java:231)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1952)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7682)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:516)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:196)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
at android.app.Instrumentation.newApplication(Instrumentation.java:1153)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1218)
... 9 more
Suppressed: java.io.IOException: Failed to open dex files from /system/priv-app/TeleService/TeleService.apk because: Failure to verify dex file '/system/priv-app/TeleService/TeleService.apk': Bad checksum (c0c2207c, expected 277e206c)
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:365)
at dalvik.system.DexFile.<init>(DexFile.java:107)
at dalvik.system.DexFile.<init>(DexFile.java:80)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:444)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:403)
at dalvik.system.DexPathList.<init>(DexPathList.java:164)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:126)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:101)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:74)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:87)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:116)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:114)
at android.app.ApplicationLoaders.getClassLoaderWithSharedLibraries(ApplicationLoaders.java:60)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:851)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:950)
at android.app.LoadedApk.getResources(LoadedApk.java:1188)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2499)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2491)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6497)
... 8 more
Here you go.
Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.
tohtorin said:
Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.
Click to expand...
Click to collapse
By what means did you do factory reset? Did you lose root?
Cowbell_Guy said:
By what means did you do factory reset? Did you lose root?
Click to expand...
Click to collapse
Nothing else helped out. Factory reset does not lose root because it keeps magisk modded boot image. You just need to install it again from magisk manager.
i had the same, and after monster process of rooting and 1:1 backup restoration (3 days), the last thing was to insert the SIM card (only after phone is secure), bang. Factory reset is something i never do unless i'm switching phone so i started checking files (same vs backup), log tracing, reverse engineering but then i quickly realized why bother if we have a patch boy - OOS Native Call Recording - here, so i just removed and installed the magisk plugin and it's fixed the problem.
So I finally got an android device where I can unlock my bootloader and have root.
I have a Sprint Samsung Galaxy S10 5G. Bootloader is unlocked - magisk is installed - riru core and rirue edxposed modules are installed (all stable builds).
I have been testing some modules out that I have used before, and they work. But randomly, no way to re-create this, I will manually reboot the phone, and it will half wipe the data. Meaning, it shows the setup app.
Looking through the logcat, it appears my user id is randomly changing.
Code:
07-28 23:59:30.043 1109 5360 E cutils : Expected path /data/data/com.samsung.android.pluginrecents with owner 10235:10235 but found 10226:10226
This makes sense, as the apps are still installed, I just can't run anything because:
Code:
07-28 23:59:30.043 1109 5360 E installd: Failed to prepare /data/data/com.samsung.android.pluginrecents: Success
07-28 23:59:30.043 1109 5360 E installd: prepare-Failed to prepare /data/data/com.samsung.android.pluginrecents: Success
07-28 23:59:30.043 17248 17346 E PackageManager: Failed to create app data for com.samsung.android.pluginrecents: com.android.server.pm.Installer$InstallerException: android.os.ServiceSpecificException: prepare-Failed to prepare /data/data/com.samsung.android.pluginrecents (code 0)
Does anyone have any idea what/why my user id is randomly changing?
Firstly, the "system" partition of official LineageOS 18.1 doesn't have enough free space for OpenGapps "stock".
Previously I've been using OpenGapps "pico" instead, then today I want to try to configure "stock" to exclude most of apps, only leaving out several wanted ones. There's an official tutorial for this: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
I modified the example "Include" mode installation config, replacing "Include" with "Exclude" & commented out apps I want to install.
After several cycles of trial-and-error process, the OpenGapps installation process finally seemed to be complete without error.
However, the phone fell into bootloop after rebooting from TWRP...
Fortunately, I was still able to adb shell into the phone, and then I got these two lines from logcat:
Code:
11-06 10:21:35.139 5990 5990 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
11-06 10:21:35.139 5990 5990 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.projection.gearhead (/system/app/AndroidAutoPrebuilt): android.permission.UPDATE_APP_OPS_STATS}
I was confused. I actually excluded "AndroidAuto" and (not mentioned in example config) "AndroidAutoPrebuiltStub" but these two unwanted apps were still automatically reinstalled during boot, even after manually deleting its files under TWRP & deleting its sections in /data/system/packages.xml. I also checked /system_root in TWRP & these two apps didn't show up there.
Finally I gave in. I commented out the lines which previously excluded these two unwanted apps in my OpenGapps config. But then the phone still fell into exactly the same bootloop syndrome.
After some googling, I edited /etc/permissions/privapp-permissions-google.xml - according to official docs, "as of Android 9, implementors must explicitly grant or deny all privileged permissions or the device won’t boot". So I added (seemed to be missing) "android.permission.UPDATE_APP_OPS_STATS" inside the "com.google.android.projection.gearhead" section.
Phew. After editing privapp-permissions-google.xml the phone finally got out of bootloop...
Ah, tried again, with "GearheadStub" included, while both "AndroidAuto" and "AndroidAutoPrebuiltStub" were excluded, this time the unedited privapp-permissions-google.xml didn't trigger a bootloop.