Develop Bugs

Android Market Error

Everytime I try to purchase an app or song or book from the market I get "An error has occurred. Please try again." Its been happening since about October. I've tried clearing the cache on the market, I tried factory resetting, I even tried wiping everything (sd and emmc included.) The log mentions something about mismatched uids.
HTML:
12-11 10:28:01.601 I/ActivityManager( 461): Starting activity: Intent { flg=0x20010000 cmp=com.android.vending/com.google.android.finsky.activities.PurchaseDialog (has extras) } from pid 1242
12-11 10:28:01.701 D/Finsky ( 1242): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update. Local Version [8009011] >= Server Version [0]
12-11 10:28:01.741 I/ActivityManager( 461): Displayed com.android.vending/com.google.android.finsky.activities.PurchaseDialog: +123ms
12-11 10:28:01.831 D/Finsky ( 1242): [1] PageFragment.rebindViews: Page [class=PurchaseFragment] loaded in [89 ms]
12-11 10:28:01.841 E/Finsky ( 1242): [1] AppPermissionAdapter.<init>: Invalid group name:null
12-11 10:28:01.871 W/Finsky ( 1242): [1] CarrierParamsAction.run: Saving carrier billing params failed.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.shouldFetchProvisioning: Required CarrierBillingParams missing. Shouldn't fetch provisioning.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.run: No need to fetch provisioning from carrier.
12-11 10:28:01.881 D/Finsky ( 1242): [1] GetBillingCountriesAction.run: Skip getting fresh list of billing countries.
12-11 10:28:01.881 W/AccountManagerService( 461): caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.881 E/Finsky ( 1242): [57] 1.run: Caught SecurityException: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 D/Finsky ( 1242): [1] CheckoutPurchase.onErrorReceived: Could not retrieve Checkout auth token: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 E/Finsky ( 1242): [1] CheckoutPurchase.setError: type=UNKNOWN, code=-1, message=An error occurred. Please try again.
Reposted to QandA, sorry for the mix up. Mods feel free to delete.

I was getting the authentication error and wouldn't log me in....I reflashed Gapps and I could get into Market again but when I try to download or update an app, it just sits there and says, "downloading......"
But my buddy who is on Sprint is able to download apps just fine.

Have you tried contacting Google via email. It might be on their end.
Sent from my ADR6300 Incredible

I believe this can be fix like so:
Go to: settings/applications/manage applications/running app./tap:download manager,then tap clear data,and force to stop,after that go back to home,restart your phone,also clear cache/data on market,I hope this will fix your problem...let me know.
Sent from my PC36100 using XDA App

Thanks for the suggestion, but I am still having the problem. I'll just use the web interface for now.

I just downloaded the MarketFix app from the Android Market. It moves the market cache to the SD card. Problem solved...give it a shot.

I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor

gadzooks64 said:
I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor
Click to expand...
Click to collapse
Thanks for the tip, but still a no go.

wrong thread, sorry

I'm having the same exact problem as the OP, anyone know of any other possible solution or tricks?
By the way I have a different device than OP, mine is a cheap chinese tablet called teclast p75.

android market place error
unfortunately i also have the issue with the android market place on my kindle fire. i installed the market place, google wallet is actual, but i am even not able to download free apps. after accepting and clicking on "download" i always get the message
"appname" could not be downloaded due to an error. does anybody have an idea? I am really lost.

have you been updated to the 3.4.7 version of the market yet? that's to anyonehaving this issue

I got same proplem. i'v update market, clear cache, clear everything and stil can't buy anythings from google play

so?
I am having this problem now. on og droid steel droid rom.

I had a similar problem once on my kindle and eventually what i wound up doing was going into recovery and flashing the ROM from scratch like it was brand new. Wipe System/Data/DataData/Cache/Dalvik/anything else you like to wipe and reflash the ROM (and the newest applicable gapps) and see if that helps. It did the trick for me, it is an odd error and I feel like the easiest thing is to start from the beginning when something like that happens and hope that you don't run into it again.
EDIT: of course make a nandroid first, in case it doesn't work

I had the mismatced UIDs issue when I installed a stock 2.3.4 Rom. It alerted me on the first boot up, then never alerted me again. I had to install a different Rom because many features didn't work. Hope this helps!

I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?

I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?
Click to expand...
Click to collapse
Were you able to root/flash this through recovery? With stock ROMs the GAPPS are typically included (unless the company making the tablet wishes to use a different market so they don't have to pay royalties to google).

Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.

kulhat said:
Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.
Click to expand...
Click to collapse
If you want to install a newer market you can do it as long as you're rooted. That being said, so long as you're not on an ancient device (maybe you're that lucky with the chinese tablet) it is supposed to update automatically. At any rate, if you have SU then you just need to drop the vending.apk into /system/app and give it the following permissions:
[X][X][ ]
[X][ ][ ]
[X][ ][ ]
EDIT: You might only need marketupdater.apk things have changed since they changed the market to googleplay so I am not as familiar with it as I used to be when I originally rooted/ added the market to my Kindle Fire
All I do anymore to get gapps is flash the gapps.zip through recovery but I don't know a whole lot about your chinese tablet so I can't really give input on its recovery setup haha

[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

[DEVS][CONTRIBUTE!] Huawei Ascend P6 Development Errors/Tips/Questions/Research

Contribute and help the other devs!​
So, I'm making this thread for any dev/rom chef/etc who want to share their tips on P6 Development. Anyone can contribute and probably will get useful for all the devs, for error preventiong etc.
Just say your tip and how you managed to got it
You can also post your researchs, kernel, rom, bootloader, etc releated (may be useful for someone) and ask for help in a dev releated issue
Everything will be added to the firsts posts (questions and solutions included), just post here or send me a PM
ERROR PREVENTION
Partition formating with updater-script:
Don't try to format /system/ (and probably /data/, /sys/ and a bunch more) via updater-script, it will CORRUPT the partition (and probably others)
Lore: I was ( @S34Qu4K3 ) trying my updater-script with a new rom, formatted /system/, /system/ partition was erased but the recovery got corrupted (and a cute bootloop too) so i needed to reflash the original recovery (and system too)
Manual push of images
Don't attemp this, our tricky phone seems to perform checksums on everything, so you will get a bootlop
Lore: @Stickman89 and me was testing manual pushing of recovery.img, after overwriting the partition, it got corrupted, so we needed to reflash recovery again
DEV TIPS
HELP REQUESTS
Requested by: @S34Qu4K3
Question: Inside UPDATE.APP files form Huawei, there's a .img called fastboot.img, somebody got info about what filesystem is? Tried unpacking methods for ext4, yaffs and all the unpack scripts that I could find, but I'm unable to view, extract or edit what's on the image.
Answer: ----
RESEARCH
Potential MHL support
Discovered by @Stickman89 , in init.k3v2oem1.rc inside boot.img there are the next lines:
Code:
#mhl
chown system system sys/devices/virtual/mhl/siI-8240/rcp_keycode
chown system system sys/devices/virtual/mhl/siI-8240/rcp_ack
chown system system sys/devices/virtual/mhl/siI-8240/devcap
What we can guess from here? Probable, there will be MHL support (maybe it's already on our kernel but it's deactivated) from Huawei

*reserved*

All can contribute! (yep, *reserved* too)

S34Qu4K3 said:
All can contribute! (yep, *reserved* too)
Click to expand...
Click to collapse
Okay this is getting incredibly frustrating, I've discovered we can't even update boot.img via recovery either (changes don't take effect). This isn't a bug in recovery it's actually Huawei's Bootloader lock in play. So that means no way to amend bootclass methods.
I've also discovered for people needing extra head-way for framework related code you can infact add it into /system/framework/hwframework.jar since if you try and add too much to framework.jar it will go stale and unable dexopt.

This is the only error stopping my ported MIUIv5 4.2.2 build from booting on the Ascend P6:
Code:
[B]E/AndroidRuntime( 9888): android.content.res.Resources$NotFoundException: Resource ID #0x6080005[/B]
E/AndroidRuntime( 9888): at android.content.res.Resources.getValue(Resources.java:1035)
E/AndroidRuntime( 9888): at android.content.res.MiuiResources.getValue(MiuiResources.java:87)
E/AndroidRuntime( 9888): at android.content.res.Resources.getInteger(Resources.java:842)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.MiuiKeyguardUpdateMonitor$1.onChange(MiuiKeyguardUpdateMonitor.java:20)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.MiuiKeyguardUpdateMonitor.<init>(MiuiKeyguardUpdateMonitor.java:30)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.KeyguardViewMediator.<init>(KeyguardViewMediator.java:457)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.MiuiKeyguardViewMediator.<init>(MiuiKeyguardViewMediator.java:19)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.PhoneWindowManager.init(PhoneWindowManager.java:1025)
E/AndroidRuntime( 9888): at com.android.internal.policy.impl.MiuiPhoneWindowManager.init(MiuiPhoneWindowManager.java:120)
E/AndroidRuntime( 9888): at com.android.server.wm.WindowManagerService$3.run(WindowManagerService.java:984)
E/AndroidRuntime( 9888): at android.os.Handler$BlockingRunnable.run(Handler.java:745)
E/AndroidRuntime( 9888): at android.os.Handler.handleCallback(Handler.java:725)
E/AndroidRuntime( 9888): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 9888): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 9888): at android.os.HandlerThread.run(HandlerThread.java:60)
The line in bold being the error ofcoarse... Strange thing is this missing resource (actually an integer) is actually not missing at all, it's there.
Shame there really isn't much information available about this, there has been a few other people who have been stumped by the very same error.
We fix this, then we'll see a booting MIUI build.

Check my posts at http://forum.xda-developers.com/showthread.php?t=2410260&page=8
They should made it more clear why u cant push images via fastboot.
Fastboot also runs only on virtual mounts thats why nothing changed.

The final answers​
i will tell u everything what ever confused u on the P6.
@S34Qu4K3
Answer for the.img and Huawei question
---------------------------------------------------------------
.img is just emulated by Goldfish u cant push it with adb.
Format is a mix from modded yaffs2 with some binary and img that it looks like native Android.
u can't extract with unyaffs2 cause they will miss mutch bytes. Try "Android SDK Emulator" for extract. The only way to see the full content is with goldfish emulators ,but care they will add a bit trash to it cause u will extract from a running system.
Potential MHL support...
MHL should be still runnig but not on the virtual Kernel . P6 running 2 at once
Please see my new post and u would understand how bad P6 really works: http://forum.xda-developers.com/showthread.php?t=2410260&page=9

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.

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.