Develop Bugs

Android Boot hangs with "disabling 'sysinit'"

I've gotten Android installed (and updated) on my HTC Tilt Device. My current hang up is that when I let it boot it hangs with the message
Code:
A N D R O I D [ ] init: cannot find'/system/bin/logwrapper', disabling 'sysinit'
Did I do something wrong/what can I do to resolve this issue?
Regards,
~Jeff

Onward, upward, backward. forward, I tried installing the "Warm Donut" version instead of the "Eclair" and the system hangs with this different message are startup on this one:
Code:
init: Unable to open persistent property directory /data/property errno: 2
I think Android dislikes me (Maybe it knows my other phone runs Maemo LOL)... Suggestions?
~Jeff

So I found a thread (which I can't link to because of the forum rules) that describes my second issue but the alternate data.img file provided does not resolve the issue for me as it says it should... As always waiting patiently and open to suggestions.
~Jeff

Since you mention data.img i'll assume you are using Haret rather then Nand install.
The 'init: Unable to open persistent property directory /data/property errno: 2' means that android cannot find the data folder, usually happens if you miss the installer stage.
Even when running from haret we have to run the installer in order to unpack the 'androidinstall.tgz' and set up the data image.
To access the installer menu you must press the d-pad centre button when booting.
Note that once it is installed you do not need to enter the installer again, unless you are updating.

Error installing Facebook on CM 12.1 (ZMoD by Ziyan)

I installed the ZMoD ROM by Ziyan a couple of weeks ago on my Galaxy Nexus. works perfect, much faster than CM 10.2 which I used before, and stable with no problems so far.
the only issue I have is that I can't install the Facebook app. when installing via Play Store, I get error 504 (which normally means that there is a network connection error, but that's not the case because I can install other apps just fine).
I then tried to sideload the app using adb, and this is the error I get after the several packages have been compiled:
Code:
E/installd( 136): DexInv: --- END '/data/app/com.facebook.katana-1/base.apk' --- status=0x0100, process failed
W/PackageManager( 414): Package couldn't be installed in /data/app/com.facebook.katana-1
E/Finsky ( 1478): [1] 2.onReceive: Error -504 while installing com.facebook.katana: INSTALL_FAILED_DEXOPT: Package couldn't be installed in /data/app/com.facebook.katana-1: scanPackageLI
W/Finsky ( 1478): [1] 3.installFailed: Install failure of com.facebook.katana: -504 null
D/Finsky ( 1478): [1] InstallerTask.cancelCleanup: Cancel running installation of com.facebook.katana (com.facebook.katana)
E/ActivityThread(19954): Failed to find provider info for com.facebook.katana.provider.AttributionIdProvider
searching the web for this error it seems that one possible cause is that the /system partition is too small, and indeed, there is hardly any space left there. I got an error about this issue when flashing the GApps, so I selected a smaller GApps build to work around it.
any ideas what can be done about this?

solved
ok, I solved the issue. for the record, I did a new install of ZMoD, but this time, I not only did the normal factory reset (i.e. clearing cache, dalvik, data), but also formatted the /system partition. looks like this removed some leftovers from the old CM version which caused the conflict.

adb restore not working

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.

Ota 10.0.6 broke my mobile data. Files needed.

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.

General Hard attempt of installing OpenGapps to LineageOS 18.1

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.