Develop Bugs

[Q] Galaxy nexus showing error after every boot

i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers

coolshan said:
i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers
Click to expand...
Click to collapse
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already

coolshan said:
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already
Click to expand...
Click to collapse
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt

Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
Petrovski80 said:
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt
Click to expand...
Click to collapse
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol

coolshan said:
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol
Click to expand...
Click to collapse
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.

Petrovski80 said:
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.
Click to expand...
Click to collapse
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/

coolshan said:
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/
Click to expand...
Click to collapse
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895

Petrovski80 said:
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"

coolshan said:
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"
Click to expand...
Click to collapse
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah me too.. thanks for the help though. but still i dont understand why is they phone functioning properly? what disfunction this process can cause ? it seems to make and receive calls and sms without any probelm

Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:

coolshan said:
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:
Click to expand...
Click to collapse
Great you fixed it. Thanks for posting the solution here.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Google Play Services crash on CM10.1

Hi,
I have recently flashed CM 10.1 stable on my Mobilicity S3 (same as T-Mobile). I keep getting crashes of the Google Location services process. I have narrowed it down to the latest Google Play Services update, if I revert the updates for Google Play Services, the crashes go away. Unfortunately this package is required by several of Google Apps (like Hangouts, Google+, ...).
I have tried wiping the device (data, cache, format system) and reinstall a fresh download of CM10.1 and the gapps, but the problem comes back when I update the Google Play services to the latest version.
The logcat shows this error:
Code:
E/AndroidRuntime( 2406): FATAL EXCEPTION: GCoreUlrInitSvc
E/AndroidRuntime( 2406): java.lang.NullPointerException
E/AndroidRuntime( 2406): at doo.a(SourceFile:120)
E/AndroidRuntime( 2406): at com.google.android.location.reporting.service.InitializerService.a(SourceFile:392)
E/AndroidRuntime( 2406): at com.google.android.location.reporting.service.InitializerService.c(SourceFile:382)
E/AndroidRuntime( 2406): at com.google.android.location.reporting.service.InitializerService.h(SourceFile:48)
E/AndroidRuntime( 2406): at dok.handleMessage(SourceFile:178)
E/AndroidRuntime( 2406): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2406): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2406): at android.os.HandlerThread.run(HandlerThread.java:60)
I also noticed that, with the latest version of the Google Play Services, 50% or more of my battery is used by the location service, so it looks like something's stuck, maybe holding a wakelock that keeps the CPU awake.
For now I have reverted the Google Play services updates, but as said it means I can't use several apps, so any hindsight on how to fix this problem would be greatly appreciated. Thanks!

Flash gapps from my signature. And get BetterBatteryStats so we can see some logs.

Thanks. I have flashed your gapps, but after upgrading Google Play Services the crashes return.
Do I need to wipe it before I flash your gapps? I didn't, I flashed the gapps on top of what I already had.

afv011 said:
Thanks. I have flashed your gapps, but after upgrading Google Play Services the crashes return.
Do I need to wipe it before I flash your gapps? I didn't, I flashed the gapps on top of what I already had.
Click to expand...
Click to collapse
If you have GMS_Core.apk in your /system/apps folder, delete and reboot (or uninstall with TiBu). I suggest wiping the data for it first.

Aerowinder said:
If you have GMS_Core.apk in your /system/apps folder, delete and reboot (or uninstall with TiBu). I suggest wiping the data for it first.
Click to expand...
Click to collapse
I had GMS_Core.apk, which I have deleted and rebooted. Same result, it crashes after I update Google Play Services. Actually, this time I did not have to update, I had to install it, and it crashed straight away, same as before, although now instead of just "OK" I have the option to report. The crash log is the same.
I'm going to wipe the device, re-install CM 10.1 and then your gapps and see what the result is.

I have reflashed and installed your gapps. So far, no crashes, but I'll have to run it a bit longer to confirm that it's fixed, but so far so good.
I'll re-install some of the apps and give it a shake down, and will report later. I will also install BetterBatteryStats to keep an eye on the battery level, but hopefully the 2 issues are related. Thanks!

So, it didn't last.
I still get crashes of location services, but now the logcat is different:
Code:
E/AndroidRuntime(10595): FATAL EXCEPTION: SyncAdapterThread-4
E/AndroidRuntime(10595): java.lang.NullPointerException
E/AndroidRuntime(10595): at dot.a(SourceFile:536)
E/AndroidRuntime(10595): at dor.a(SourceFile:131)
E/AndroidRuntime(10595): at dor.onPerformSync(SourceFile:75)
E/AndroidRuntime(10595): at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:254)
I don't see the previous crashlog now, so something's different. Any idea what the problem could be this time?

afv011 said:
So, it didn't last.
I still get crashes of location services, but now the logcat is different:
Code:
E/AndroidRuntime(10595): FATAL EXCEPTION: SyncAdapterThread-4
E/AndroidRuntime(10595): java.lang.NullPointerException
E/AndroidRuntime(10595): at dot.a(SourceFile:536)
E/AndroidRuntime(10595): at dor.a(SourceFile:131)
E/AndroidRuntime(10595): at dor.onPerformSync(SourceFile:75)
E/AndroidRuntime(10595): at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:254)
I don't see the previous crashlog now, so something's different. Any idea what the problem could be this time?
Click to expand...
Click to collapse
Did you factory reset?

Aerowinder said:
Did you factory reset?
Click to expand...
Click to collapse
Yes, I wiped (clear data/cache, format system, wipe dalvik) and re-install, CM10.1 then gapps.
The crashed happened after I installed gmail and enable sync, which would line-up with the crashlog, though I don't see how that's related to the location services.
The crash has occurred twice, but in the last couple of hours it's been working fine without any issues, and so far I don't see Location Services at the top of my battery stats.
I'll keep using the phone normally and see if the crash returns. It's definitively better than before, where it would crash every few minutes.

No further crashes, so I think it should be good now. Thanks for your help, the gapps you provided saved the day.

Help recoving bricked phone

My Captivate Glide is running Cyanogenmod and has TWRP recovery installed. After a reboot yesterday it now won't boot - it just sets at the spinning Cyanogenmod logo forever. It was hard-reset by accident (power+volume) so I suspect some kind of corruption, and I'd prefer not to have to wipe the whole phone.
Unfortunately, I can't get a logcat of the boot because adb reports the device as "unauthorized", and obviously I can't authorise it since it doesn't finish booting. So I have no way to know what's actually broken.
Does anyone have any ideas, short of a full wipe? Thanks.

FireFury said:
My Captivate Glide is running Cyanogenmod and has TWRP recovery installed. After a reboot yesterday it now won't boot - it just sets at the spinning Cyanogenmod logo forever. It was hard-reset by accident (power+volume) so I suspect some kind of corruption, and I'd prefer not to have to wipe the whole phone.
Unfortunately, I can't get a logcat of the boot because adb reports the device as "unauthorized", and obviously I can't authorise it since it doesn't finish booting. So I have no way to know what's actually broken.
Does anyone have any ideas, short of a full wipe? Thanks.
Click to expand...
Click to collapse
Go into TWRP:
Wipe cache and dalvikcache and try again. This does not destroy any user data and is safe to use. This may fixes your problem already.
If that doesn't help:
Boot up until the boot loop occurs then press a long time the power button until the device reboots. Then directly go again into TWRP again. It is important that you do NOT remove battery or power off the device!
Then in twrp execute:
adb shell "cat /proc/last_km*" > kernel.log
And attach the resulting kernel.log file here.
.

FireFury said:
My Captivate Glide is running Cyanogenmod and has TWRP recovery installed. After a reboot yesterday it now won't boot - it just sets at the spinning Cyanogenmod logo forever. It was hard-reset by accident (power+volume) so I suspect some kind of corruption, and I'd prefer not to have to wipe the whole phone.
Unfortunately, I can't get a logcat of the boot because adb reports the device as "unauthorized", and obviously I can't authorise it since it doesn't finish booting. So I have no way to know what's actually broken.
Does anyone have any ideas, short of a full wipe? Thanks.
Click to expand...
Click to collapse
Go into TWRP:
Wipe cache and dalvikcache and try again. This does not destroy any user data and is safe to use. This may fixes your problem already.
If that doesn't help:
Boot up until the boot loop occurs then press a long time the power button until the device reboots. Then directly go again into TWRP again. It is important that you do NOT remove battery or power off the device!
Then in twrp execute:
adb shell "cat /proc/last_km*" > kernel.log
And attach the resulting kernel.log file here.
.
Click to expand...
Click to collapse
any update on this?

Sorry for the radio silence...
xdajog said:
Go into TWRP:
Wipe cache and dalvikcache and try again. This does not destroy any user data and is safe to use. This may fixes your problem already.
Click to expand...
Click to collapse
This was the first thing I tried, but it doesn't help - after wiping the caches and rebooting I get the normal "optimising apps" screen, but after that finishes it starts the boot animation again instead of going to the android UI.
Boot up until the boot loop occurs then press a long time the power button until the device reboots. Then directly go again into TWRP again. It is important that you do NOT remove battery or power off the device!
Then in twrp execute:
adb shell "cat /proc/last_km*" > kernel.log
And attach the resulting kernel.log file here.
Click to expand...
Click to collapse
There's no last_kmsg file in /proc. But I manually imported my workstation's ADB key into the phone through TWRP and can now get a logcat (attached). I'm still stumped though - it looks like it times out accessing com.android.internal.backup.LocalTransportService and then kills off system_server. No indication as to why though.
It might be irrelevant, but "W/WallpaperService( 422): no current wallpaper -- first boot?" also sounds odd since I do have wallpaper. It logs into the wifi automatically, and the ssh server is running so I can get a shell on the device at least. The internal and external SD cards appear to be unmounted.

FireFury said:
Sorry for the radio silence...
This was the first thing I tried, but it doesn't help - after wiping the caches and rebooting I get the normal "optimising apps" screen, but after that finishes it starts the boot animation again instead of going to the android UI.
There's no last_kmsg file in /proc. But I manually imported my workstation's ADB key into the phone through TWRP and can now get a logcat (attached). I'm still stumped though - it looks like it times out accessing com.android.internal.backup.LocalTransportService and then kills off system_server. No indication as to why though.
It might be irrelevant, but "W/WallpaperService( 422): no current wallpaper -- first boot?" also sounds odd since I do have wallpaper. It logs into the wifi automatically, and the ssh server is running so I can get a shell on the device at least. The internal and external SD cards appear to be unmounted.
Click to expand...
Click to collapse
Hi,
thanks for providing the logcat.
I'm not an expert on this but it may be caused by this:
Code:
F/libc ( 424): Fatal signal 6 (SIGABRT) at 0x000001a8 (code=0), thread 424 (system_server)
E/ActivityManager( 424): ANR in system
E/ActivityManager( 424): [COLOR="red"][B]PID: 424[/B][/COLOR]
E/ActivityManager( 424): Reason: Executing service android/com.android.internal.backup.LocalTransportService
and then
Code:
I/DEBUG ( 117): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 117): Build fingerprint: 'Samsung/cm_i927/i927:4.4.3/KTU84M/4fcf597a69:userdebug/test-keys'
I/DEBUG ( 117): Revision: '14'
I/DEBUG ( 117): [B][COLOR="Red"]pid: 424,[/COLOR][/B] tid: 424, name: system_server >>> system_server <<<
I/DEBUG ( 117): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG ( 117): r0 00000000 r1 beca0448 r2 400a3570 r3 515a1880
I/DEBUG ( 117): r4 415f1370 r5 52b784e8 r6 00000002 r7 000000c3
Which is a back trace showing the system_server process dies.
I see also this:
Code:
E/ActivityManager( 424): Error reading /data/anr/traces.txt
E/ActivityManager( 424):[B][COLOR="Red"] java.io.FileNotFoundException: /data/anr/traces.txt[/COLOR][/B]: open failed: ENOENT (No such file or directory)
E/ActivityManager( 424): at libcore.io.IoBridge.open(IoBridge.java:409)
E/ActivityManager( 424): at java.io.FileInputStream.<init>(FileInputStream.java:78)
E/ActivityManager( 424): at android.os.FileUtils.readTextFile(FileUtils.java:236)
E/ActivityManager( 424): at com.android.server.am.ActivityManagerService$18.run(ActivityManagerService.java:10121)
E/ActivityManager( 424): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
So how to fix your problem? To be honest I'm not sure. :laugh:
The first thing I would try is to mount the /data partition in TWRP and create a trace file:
mount /data
mkdir /data/anr (this may exists already)
touch /data/anr/traces.txt
The file is like the name states for logging things so it will not solve anything.
Well but maybe that helps not letting the process die.
Code:
E/ActivityManager( 424): Reason: Executing service android/com.android.internal.backup.LocalTransportService
Because of the above I believe you may have most success with this:
You could check (also in TWRP) the /data/data/ (yeah /data/data) directory and search for "com.android.internal.backup" or similar.
I do not use that app which comes from Google so I cannot tell you the exact name. I would rename that folder which removes your backup settings (if you configured the backup service).
If all those do not help you could remove the backup app completely from /system/apps/ (in my case it is e.g. GoogleBackupTransport.apk)
Attach again a logcat and it would be also helpful if you can then also do a "adb shell dmesg > dmesg.log" when booting.
.

Thank for the help. Looks like something in /data/system is broken - blowing away that directory and letting it get recreated seems to fix it all. I couldn't figure out what specifically was broken though.

FireFury said:
Thank for the help. Looks like something in /data/system is broken - blowing away that directory and letting it get recreated seems to fix it all. I couldn't figure out what specifically was broken though.
Click to expand...
Click to collapse
Well yes that is the hard way isn't it? Means you will loose all your phone settings afaik?
.

xdajog said:
Well yes that is the hard way isn't it? Means you will loose all your phone settings afaik?
Click to expand...
Click to collapse
Well, I've lost a lot of phone settings and app settings, but not all. I'm actually a bit confused about what I've lost - I expected to lose my phone settings, but I thought app specific stuff was under /data/user/0 so I didn't expect to lose my app settings. But some app settings are gone, none the less. Maybe having to recreate /data/system has prompted it to reinitialise a lot of the other databases too...

I've actually got a backup of the whole of /data from before it broke, which I could restore. But I'm pretty sure TWRP's fix_permissions doesn't work (at least, it didn't set the ownerships on /data/system - I had to do that manually) so getting the permissions right after restoring it could be a pain.

Well yes there are databases within /data which can get corrupted thats why a factory reset which cleans /data will help in those cases. You had removed /data/system so you will loose settings but not all as you seen already.
Can you live with it like it is atm ?
.

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.