Related
Hi,
I'm trying to install a apk but it gives me a error:
"Application not installed"
I can see in the logcat:
Code:
E/PackageManager( 1330): Package com.tencent.launcher requires unavailable feature android.hardware.camera.autofocus; failing!
W/PackageManager( 1330): Package couldn't be installed in /data/app/com.tencent.launcher-1.apk
It seems that the apk search android.hardware.camera.autofocus and doesnt find it.
Can you help me please?
Many thanks and sorry for my english!
I find this error message is fully clear.
The developer of the TencentDesktop was to lazy to go through all the rights he requests
and so the software is not installable on devices without autofocus.
As Archos doesn't have autofocus......
You could change that flag with ApkEdit and see if it will work then.
http://forum.xda-developers.com/showthread.php?t=890199
com.bn.cloud.svc permission issue: What does a healthy ''packages.xml" look like?
I'm running a rooted Nook 1.4.3, and somewhere in my customization, I've run into an odd permissions issue.
Main question: Can anyone with a Nook 1.4.3 whose B&N Shop is working paste their /data/system/packages.xml here so I can check mine against it?
Main problem: The B&N Shop can't connect to anything. Basically my device has no access to the B&N cloud.
Looking at the logs, I see this a lot:
Code:
W/ActivityManager( 1294): Unable to start service Intent { act=com.bn.cloud.IRequestHandler }: not found
Looking at logcat while the tablet boots, I see this related section:
Code:
I/PackageManagerService( 1294): /system/app/BnCloudRequestSvc.apk changed; collecting certs
W/PackageManagerService( 1294): Signature mismatch for shared user : SharedUserSetting{40597710 com.bn.cloud/10032}
E/PackageManagerService( 1294): Package com.bn.cloud.svc has no signatures that match those in shared user com.bn.cloud; ignoring!
...
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.drpreader
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.RECEIVE_NOTIFICATION in package com.bn.nook.drpreader
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.social
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.quickstart
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.RECEIVE_NOTIFICATION in package com.bn.nook.quickstart
W/PackageManagerService( 1294): Unknown permission com.bn.cloud.EXECUTE_REQUEST in package com.bn.nook.reader.activities
So my best guess is that I borked something in my packages.xml so PackageManager thinks my 'BnCloudRequestSvc.apk' is wrong and completely disables the cloud service that the shop (and other com.bn.* apps) need.
I've tried wiping my dalvik cache and running 'fix_permissions' from the bootable CWM sdcard I used to root the thing, but still no luck.
I'd love to compare my packages.xml to someone who has a working shop, or hear any other suggestions anyone may have about what may be going wrong here, like why does the Package Manager say "/system/app/BnCloudRequestSvc.apk changed; collecting certs"?
Solved!
I solved this issue by doing the following:
Delete /data/system/packages.xml
Reboot -> This regenerates /data/system/packages.xml (ignore all force-closes, they are expected)
Power off
Power on with CWM SD Card, go into "advanced" and "Fix Permissions" (Built my SD Card using these instructions: http://forum.xda-developers.com/showthread.php?t=1466583)
Reboot
Once it came back up, everything was working great!(*)
(*) One small caveat-> After that last reboot, it came up with the 'Homecatcher" app doing something incredibly weird: It was flickering and I couldn't actually choose a launcher... Thankfully I happened to reorient from portrait to landscape, then back to portrait, and it came out of it and began working just fine.
Now that I have the thing working again, I've compared my prevous "broken" packages.xml to the new working packages.xml, and found that my actual original problem was that I was missing a <packace> section for the com.bn.cloud.svc library.
That wasn't *quite* all...
Noting further steps here I had to take to get everything working again after this issue... escapde.
Removing packages.xml and running 'fix permissions' isn't quite the whole story. I also had to:
Reinstall all local apps to re-request their permissions:
Code:
[in adb shell]:
for app in /data/apps/*.apk; do pm install -r $app; done
Modify the permissions of all existing downloaded books and magazines in /data/media so it matches the new B&N UID:
Code:
[in adb shell]:
busybox ps
... Find the UID that all the com.bn.* apps are running with
... In my case this was '10020', aka 'app_20'
busybox chmod 10020.10020 -R /data/media/Books/*
busybox chmod 10020.10020 -R /data/media/Magazines/*
Hi everyone
I decided to post here because I couldn't resolve my problem with only tutorials.
I have an HTC Legend which was very slow, because of an update from SFR. I tryed a factory reset but it was still slow.
I did a backup with clockworkmod, so I can always go back to the first (bad) configuration.
Today, after many operations, the phone boots until the first screen (when you have to use the slide to unlock the screen). But the screen doesn't respond and the reboot reboot after few minutes. Even after using a RUU...
I know that it is possible to restore it, because it worked once. But because of my enthusiasm, I broke the configuration with cyanogen. (I didn't made backup, so stupid)
If even a RUU cannot restore my HTC Legend, what can I do?
Thank you in advance
Useful information:
HTC Legend branded (Vodafone)
Actual HBOOT version: 1.00
Radio: 7.13.35.05
S-ON
Neferth said:
If even a RUU cannot restore my HTC Legend, what can I do?
Click to expand...
Click to collapse
Hello Neferth,
Switch off your phone. Than switch it on holding the "Vol-" and the "power" button. Then select recovery.
At the red [!] screen. press "Vol+" and the "power" button.
Wait for a blue menu list at the top of the screen. Then select update.zip.
Then you can see the ClockworkMod Recovery menu. You can do a restore now ...
Greetings: alligator-asl
Hi,
If I do that, I can only backup my phone to the first (and bad) configuration. And the phone still boots in loop...
I search for a solution to completely format the system and wipe all things I added. I believed that a RUU could help me, but the problem still remains, as if I forgot something. This is despairing...
Neferth said:
Hi,
If I do that, I can only backup my phone to the first (and bad) configuration. And the phone still boots in loop...
I search for a solution to completely format the system and wipe all things I added. I believed that a RUU could help me, but the problem still remains, as if I forgot something. This is despairing...
Click to expand...
Click to collapse
Here's an idea, you can boot into clock work mod yeah? OK, pick a rom, any rom, but I'd advise you to get one of the froyo based roms like blay0s, these are probably better for you at this stage as they are compleat, and dare I say it bug free
Anyway download the zip file, put it onto your sdcard, boot into recovery, format boot, system, data, cache, and sdext NOT THE SD CARD!
now flash the zip file and reboot, if you still have boot loop then its possible your internal rom space is damaged, I've heard of this issue in other phone threads, however I've not yet heard a story about damaged rom space on legend.
Sent from my Legend using xda app-developers app
Thanks you for your help!
I followed your instructions and I:
-rooted my phone with r4legend.
-formatted boot, system, data and cache partition
-installed Bay0 O.8 and upgraded it to 0.8.4
The bootloop seems to be fixed, but the phone still freeze at first screen. Moreover, the screen dies out after few minutes.
Just in case, I launched
Code:
adb logcat
, and I noticed the following errors and fails:
Code:
--------- beginning of /dev/log/system
I/Vold ( 150): Vold 2.1 (the revenge) firing up
D/Vold ( 150): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/SystemServer( 189): Entered the Android system server!
I/SystemServer( 189): Entropy Service
W/EntropyService( 189): unable to load initial entropy (first boot?)
[...]
E/ConnectivityService( 189): Error in radioAttributes - ignoring attempt to define type 6
E/ConnectivityService( 189): Error in networkAttributes - ignoring attempt to adopt radio 6
[...]
/SystemServer( 189): HTC Checkin Service.
I/SystemServer( 189): Wallpaper Service
W/WallpaperService( 189): failed parsing /data/system/wallpaper_info.xml java.io.FileNotFoundException: /data/system/wallpaper_info.xml (No such file or directory)
I/SystemServer( 189): Audio Service
[...]
I/WindowManager( 189): SAFE MODE not enabled
W/DevicePolicyManagerService( 189): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
V/KeyguardViewMediator( 189): password timeout delay 281859ms
[...]
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): !!! Unable to find ITelephony interface !!!
And when the screen dies out:
Code:
W/PackageManager( 897): Unknown permission android.permission.ACCESS_LOCATION in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission android.permission.ACCESS_GPS in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.READ_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.WRITE_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.CustomizationSetup
W/PackageManager( 897): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.android.packageinstaller (protectionLevel=2 flags=0xbe45)
W/PackageManager( 897): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.android.htcime
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.UpgradeSetup
W/PackageManager( 897): Unknown permission com.android.providers.htccdma.Specific in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.htc.VzWBackupAssistantClient.PROVISION in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.WRITE_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.ACCESS_PROVIDER in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.voicesearch
Perhaps I am wrong but I see nothing that prevent the phone from booting...
You also talked about internal rom space, what is it exactly? Because I only know the partitions:
• /boot
• /cache
• /data
• /misc
• /recovery
• /system
Where can I find this internal rom space and how can I repair it?
Neferth said:
Thanks you for your help!
I followed your instructions and I:
-rooted my phone with r4legend.
-formatted boot, system, data and cache partition
-installed Bay0 O.8 and upgraded it to 0.8.4
The bootloop seems to be fixed, but the phone still freeze at first screen. Moreover, the screen dies out after few minutes.
Just in case, I launched
Code:
adb logcat
, and I noticed the following errors and fails:
Code:
--------- beginning of /dev/log/system
I/Vold ( 150): Vold 2.1 (the revenge) firing up
D/Vold ( 150): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/SystemServer( 189): Entered the Android system server!
I/SystemServer( 189): Entropy Service
W/EntropyService( 189): unable to load initial entropy (first boot?)
[...]
E/ConnectivityService( 189): Error in radioAttributes - ignoring attempt to define type 6
E/ConnectivityService( 189): Error in networkAttributes - ignoring attempt to adopt radio 6
[...]
/SystemServer( 189): HTC Checkin Service.
I/SystemServer( 189): Wallpaper Service
W/WallpaperService( 189): failed parsing /data/system/wallpaper_info.xml java.io.FileNotFoundException: /data/system/wallpaper_info.xml (No such file or directory)
I/SystemServer( 189): Audio Service
[...]
I/WindowManager( 189): SAFE MODE not enabled
W/DevicePolicyManagerService( 189): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
V/KeyguardViewMediator( 189): password timeout delay 281859ms
[...]
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): !!! Unable to find ITelephony interface !!!
And when the screen dies out:
Code:
W/PackageManager( 897): Unknown permission android.permission.ACCESS_LOCATION in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission android.permission.ACCESS_GPS in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.READ_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.WRITE_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.CustomizationSetup
W/PackageManager( 897): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.android.packageinstaller (protectionLevel=2 flags=0xbe45)
W/PackageManager( 897): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.android.htcime
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.UpgradeSetup
W/PackageManager( 897): Unknown permission com.android.providers.htccdma.Specific in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.htc.VzWBackupAssistantClient.PROVISION in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.WRITE_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.ACCESS_PROVIDER in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.voicesearch
Perhaps I am wrong but I see nothing that prevent the phone from booting...
You also talked about internal rom space, what is it exactly? Because I only know the partitions:
• /boot
• /cache
• /data
• /misc
• /recovery
• /system
Where can I find this internal rom space and how can I repair it?
Click to expand...
Click to collapse
Well, rom space (memory storage) is the location of where your rom is flashed to, as far as I know once this is damaged there is no way to fix it.
I'm pretty sure that the boot, system, misc, recovery is all part of rom space. I'm pretty sure that data and cache is part of internal memory?
I haven't actually gotten that deep into internal workings of the hardware so I could be wrong.
Sent from my Legend using xda app-developers app
Found it. It was bad blocks on the system and data partition.
Just THANK to you for your tips and AngelDeath for his marvellous article:
http://forum.xda-developers.com/showthread.php?t=1189544
I will try to move /system and /data partitions to SD card.
edit: I will follow this tutorial => http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
edit 2: Launching a /system partition on SD card seems to be possible => http://forum.xda-developers.com/showthread.php?t=779274
But it isn't user frienldy enough, so I will probably try "task 29" with MTTY to format the partition. The bad blocks will not disappear, but I hope the system will mark them as "bad".
=> http://forum.xda-developers.com/showthread.php?t=540290
=> http://forum.xda-developers.com/showthread.php?t=644781
Is it working now? I'm also getting problems with bad blocks now
Sent from my Legend using xda premium
Hello xennr3
Sorry for the delay, I had examinations and I forgot this painful problem...
I tried to use MTTY but XP/Seven didn't let me create ActiveSync connection (making a banal connection is too hard for these OS). And without ActiveSync, no mtty.
And obviously no documentation in order to make the same thing with linux.
Sigh.
Anyway, I returned the HTC to its owner. I will try later (~3 month), but I surely will not give up. I will update this post if I found any useful documentation or alternative.
Neferth said:
Hello xennr3
Sorry for the delay, I had examinations and I forgot this painful problem...
I tried to use MTTY but XP/Seven didn't let me create ActiveSync connection (making a banal connection is too hard for these OS). And without ActiveSync, no mtty.
And obviously no documentation in order to make the same thing with linux.
Sigh.
Anyway, I returned the HTC to its owner. I will try later (~3 month), but I surely will not give up. I will update this post if I found any useful documentation or alternative.
Click to expand...
Click to collapse
Isn't active sync for connecting to windows mobile devices like GPS etc?
Sent from my Legend using xda app-developers app
I have got a Android Box i.e. MXQ Pro+ 4K from China, which is working fine except one problem of Google PlayStore updating itself to an incompatible version again and again.
It came with PlayStore 5.1.x version which was automatically updated to the "7.5.08.M-xhdpi [8] [PR] 146162341" (latest) but 8 is indicating that its for Android TV. Now when I try to run PlayStore it gives message "This app is incompatible with this device....".
Since the box is already rooted so I installed PlayStore version 7.5.08.M-all [0] [PR] 146162341 by downloading and then moving to system apps. This version works fine but with in no time it updates it self again to version mentioned above (8 for TV) and stops working.
I tried couple of methods by creating empty folder with apk name and terminal emulator using chttr command etc but nothing worked till now.
Now every time when I have to use the PlayStore, I used to uninstall updated then run. Please suggest any possible solutions.
Thanks,
Hi, have a look here
http://android.stackexchange.com/qu...-stop-google-play-from-automatically-updating
vpandey said:
I have got a Android Box i.e. MXQ Pro+ 4K from China, which is working fine except one problem of Google PlayStore updating itself to an incompatible version again and again.
It came with PlayStore 5.1.x version which was automatically updated to the "7.5.08.M-xhdpi [8] [PR] 146162341" (latest) but 8 is indicating that its for Android TV. Now when I try to run PlayStore it gives message "This app is incompatible with this device....".
Since the box is already rooted so I installed PlayStore version 7.5.08.M-all [0] [PR] 146162341 by downloading and then moving to system apps. This version works fine but with in no time it updates it self again to version mentioned above (8 for TV) and stops working.
I tried couple of methods by creating empty folder with apk name and terminal emulator using chttr command etc but nothing worked till now.
Now every time when I have to use the PlayStore, I used to uninstall updated then run. Please suggest any possible solutions.
Thanks,
Click to expand...
Click to collapse
Tried all the methods given on that page but it seems nothing is working. PlayStore now makes new folders for updating it self to latest version. Like com.android.vending-2 , ...vending-3, vending-4 and so on.
starkman said:
Hi, have a look here
http://android.stackexchange.com/qu...-stop-google-play-from-automatically-updating
Click to expand...
Click to collapse
I have the same problem but my model is t95n mini m8s(s905x version). Is there a setting that was changed that makes playstore thinks it is an android tv device? The device came with the tv version of youtube.
Edit: Look another guy with the problem. Could this be a problem with the latest play store?
https://forum.xda-developers.com/an...xqpro-google-play-store-giving-error-t3562673
Same problem
I also have the same problem. Any updates on this?
ThuG_PoeT said:
I also have the same problem. Any updates on this?
Click to expand...
Click to collapse
you can try uninstall updated on play services and also on google play, and then maybe it will work. Please get the answer if it's working on not, because is here another solution, you can change some lines on build.prop file in system folder and also added new permission which is included in Android TV, and then you will have playstore like for android TV with android TV content.
Try to find the plalystore apk folder from stock rom for example system/priv-app/phonesky/phonesky.apk (this for h96 pro+) backup it on another folder with rootexplorer...
Use aptoide to update it you will receive an error like app cant install, you will receive this warning every time that try update it, even with the versions most new.
Find downloaded playstore.apk on sdcard .aptoide folder and rename it with the name of the older phonesky.apk.
If you are root try uninstalling playstore with root uninstaller, the folder that contains the old phonesky.apk will be empty (system/priv-app/phonesky/)... you can now copy the new playstore renamed (phonesky.apk) to this folder.
After this, you now try to install newest playstore as system app with root uninstaller with the installer tab, when the process is completed push reboot now.
At this way I have get working the latest version of the playstore 7.9.30 without any errors, you must repeat all process everytime aptoide find new update of playstore
srclooney said:
Try to find the plalystore apk folder from stock rom for example system/priv-app/phonesky/phonesky.apk (this for h96 pro+) backup it on another folder with rootexplorer...
Use aptoide to update it you will receive an error like app cant install, you will receive this warning every time that try update it, even with the versions most new.
Find downloaded playstore.apk on sdcard .aptoide folder and rename it with the name of the older phonesky.apk.
If you are root try uninstalling playstore with root uninstaller, the folder that contains the old phonesky.apk will be empty (system/priv-app/phonesky/)... you can now copy the new playstore renamed (phonesky.apk) to this folder.
After this, you now try to install newest playstore as system app with root uninstaller with the installer tab, when the process is completed push reboot now.
At this way I have get working the latest version of the playstore 7.9.30 without any errors, you must repeat all process everytime aptoide find new update of playstore
Click to expand...
Click to collapse
Thanks!!!!!!! i wasnt able to install the new version of playstore in the same android tv the h96 pro+ but with your steps i was able to update it.
in the step of installing the new version with the instaler i drop me the same error when i was triying to update normally i reboot it and then appeared the mensage of Optimizing applications and then the playstore icon changed to the new and it works!!!
Barquillo said:
Thanks!!!!!!! i wasnt able to install the new version of playstore in the same android tv the h96 pro+ but with your steps i was able to update it.
in the step of installing the new version with the instaler i drop me the same error when i was triying to update normally i reboot it and then appeared the mensage of Optimizing applications and then the playstore icon changed to the new and it works!!!
Click to expand...
Click to collapse
Me alegro mucho de que te funcionara.
TX5/8 Marshmallow Google Play won't update install_failed_package_changed
So I've been struggling with the dreaded constant "Unfortunately, Google Play store has stopped" message on two IPTV boxes, a TX5pro and TX8 both running Marshmallow. The first time it happened, I came to the conclusion that the Google Play Store added a feature which requires an update that fails to install. Prior to this I had no idea that it could NOT self-update, so the problem existed from day one.
The Google Play Store has both a system and update component which exist in different locations. The system one resides at /system/priv-app/Phonesky/Phonesky.apk while the update apk should be located at /data/app/com.android.vending-[#]. In my case the latter does not exist.
Oddly Google Play Services has the same framework of system app at /system/priv-app/Prebuilt-gms-core.apk but it does have an update entry at /data/app/com.google.android.gms-[#]. It's important to note that the Google Play Store app is the only one I've encountered problems with installing or updating.
I've compared directory and file permissions/owners/attributes, from a known working rooted tablet on Marshmallow, and found nothing out of the ordinary.
Using a root terminal emulator with Unknown Sources enabled, if I use the command "pm install Phonesky.apk" the error message is "install_failed_package_changed".
I can use these commands in the terminal to manually update the Play Store:
Code:
su
mount -o remount,rw /system
cp /sdcard/Download/Phonesky.apk /system/priv-app/Phonesky/Phonesky.apk
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
mount -o remount,ro /system
reboot
A more thorough version which clears the dalvik:
Code:
su
mount -o remount,rw /system
rm /data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
rm /data/dalvik-cache/profiles/com.android.vending
rm /system/priv-app/Phonesky/Phonesky.apk
mount -o remount,ro /system
reboot
(after reboot)
su
mount -o remount,rw /system
cp /sdcard/Download/Phonesky.apk /system/priv-app/Phonesky/Phonesky.apk
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
mount -o remount,ro /system
reboot
While both manual update methods work there is a crucial problem that becomes apparent when one compares the contents of the folders /system/priv-app/Phonesky/Phonesky.apk and /data/app/com.android.vending-[#]. The former contains just Phonesky.apk while that latter has the same as base.apk but it also extracts some of the libraries and other data. I suspect that the libraries are linked so that the ones in the update folder take precedence over those installed in system locations.
With the recent addition of Google's malware detection system "Play Protect", I think updating Phonesky.apk without extracting those libraries and giving them precedence is the cause of the "Unfortunately, Google Play store has stopped" message.
I decided to install an opengapps package using the RTAndroid Linux script https://github.com/RTAndroid/android_vendor_brcm_rpi3_scripts and that's resolved my "Unfortunately, Google Play store has stopped" message for now. The Play Store still won't self update and these appear to be the relevant log events.
Code:
09-08 06:16:30.951 D/DownloadManager( 4671): [1277] Finished with status SUCCESS
09-08 06:16:31.008 I/Finsky ( 7340): [1] com.google.android.finsky.download.DownloadBroadcastReceiver.a(12): Intent received at DownloadBroadcastReceiver
09-08 06:16:31.011 I/Finsky ( 7340): [1] com.google.android.finsky.download.n.a(116): com.android.vending: onProgress 18815483/18815483 Status: 200.
09-08 06:16:31.016 I/Finsky ( 7340): [1] com.google.android.finsky.download.e.a(49): com.android.vending from 2 to 3.
09-08 06:16:31.017 I/Finsky ( 7340): [1] com.google.android.finsky.download.n.e(144): com.android.vending: onComplete
09-08 06:16:31.017 I/Finsky ( 7340): [1] com.google.android.finsky.download.n.i(89): Download com.android.vending removed from DownloadQueue
09-08 06:16:31.018 I/installd( 3807): free_cache(0) avail 25029062656
09-08 06:16:31.020 I/Finsky ( 7340): [1] com.google.android.finsky.cc.a.f.onPostExecute(6): Self-update ready to be installed, waiting for market to close.
09-08 06:16:41.194 I/installd( 3807): free_cache(18815483) avail 25029054464
09-08 06:16:43.410 W/PackageManager( 6154): installPackageLI
09-08 06:16:43.431 I/art ( 6154): Starting a blocking GC Explicit
09-08 06:16:43.533 I/art ( 6154): Explicit concurrent mark sweep GC freed 152350(6MB) AllocSpace objects, 1(244KB) LOS objects, 33% free, 15MB/23MB, paused 1.684ms total 101.885ms
09-08 06:16:43.533 E/installd( 3807): Couldn't opendir /data/app/vmdl1199500518.tmp: No such file or directory
09-08 06:16:43.546 W/Finsky ( 7340): [1] com.google.android.finsky.cc.a.n.onReceive(14): Unable to abandon session 1199500518: java.lang.SecurityException: Caller has no access to session 1199500518
09-08 06:16:43.546 E/Finsky ( 7340): [1] com.google.android.finsky.cc.a.n.onReceive(27): Error -504 while installing com.android.vending: INSTALL_FAILED_PACKAGE_CHANGED: installPackageLI
09-08 06:18:02.318 I/Finsky ( 7340): [769] com.google.android.finsky.flushlogs.FlushLogsReceiver$FlushLogsService.onHandleIntent(10): Flushing event logs for []
09-08 06:18:02.319 I/PlayCommon( 7340): [722] com.google.android.play.a.g.e(244): Preparing logs for uploading
09-08 06:18:02.319 W/art ( 6359): Long monitor contention event with owner method=int libcore.io.Posix.readBytes(java.io.FileDescriptor, java.lang.Object, int, int) from Posix.java:4294967294 waiters=0 for 3.158s
09-08 06:18:02.328 I/PlayCommon( 7340): [770] com.google.android.play.a.g.e(244): Preparing logs for uploading
09-08 06:18:02.329 I/PlayCommon( 7340): [770] com.google.android.play.a.g.e(248): No file ready to send
09-08 06:18:02.339 D/su ( 7455): sending code
09-08 06:18:02.354 D/su ( 7457): child exited
09-08 06:18:02.354 D/su ( 7458): client exited 0
As a final note and warning, using the RTAndroid update script requires editing the bash script to identify the proper TIMESTAMP="20170907" VERSION="6.0" and VARIANT="pico" which can be derived from the list: https://github.com/opengapps/arm/releases/
The final part of the script fails and causes a constant "unfortunately setup wizard has stopped" after reboot which is fixed by enabling all "App Permissions" for the system app "Setup Wizard" (Contacts, Phone).
srclooney said:
Me alegro mucho de que te funcionara.
Click to expand...
Click to collapse
hello! For me doesn't work. The first method I go to the download files (I can't find anywhere the aptoide folder) and when I copy to the play store folder I just get that must be rooted first...
There are a zip with root flashable across the stock recovery for amlogic devices try search it on google.
The metod now is very easy copy playstore or renamed playstore.apk to the system/priv app/folder of play store ....and reboot.
srclooney said:
There are a zip with root flashable across the stock recovery for amlogic devices try search it on google.
The metod now is very easy copy playstore or renamed playstore.apk to the system/priv app/folder of play store ....and reboot.
Click to expand...
Click to collapse
but I must be rooted for that method right?
Yes, must be rooted
Hello, I have similar problem that Google play Store doesn't update itself on MXQ Pro 4K RK3229 Android 7 and I can't update even when installing from apk. I can only update it using root explorer and copying new version to system. I tried running adb logcat while running the update from apk and here is what it says:
11-23 01:38:19.098 515 541 D tangzh : ttttt forbid google play update!
11-23 01:38:19.098 515 541 W PackageManager: installPackageLI
11-23 01:38:19.159 183 183 E : Couldn't opendir /data/app/vmdl68316306.tmp: No such file or directory
11-23 01:38:19.185 3733 3733 D InstallAppProgress: Installation error code: 4
Click to expand...
Click to collapse
What is this "tangzh". Seems that it's blocking the update. Any one knows if it's possible to remove this block?
Hello sir in my phone i downloading any ap from playstore it starting but stock in 95 or 90 please tellme what do i do now
You may have encountered app installation failures during app development. Lets take a look at some of the most often reported errors on Huawei devices, what they mean and how you as a developer can fix them!
The app package is invalid, incomplete, or incompatible with the operating system (result code: -2).
Cause analysis: An invalid package is uploaded for a third-party app.
Solution: Upload a valid app package.
Insufficient storage space (result code: -4).
Cause analysis: The storage space is insufficient for installing an app.
Solution: Open Optimizer and tap Cleanup to free up some storage space on your phone.
An app with the same package name has already been installed on the device (result code: -5).
Cause analysis: The app cannot be installed as the package name already exists.
Solution: Change the package name to a new one.
Incompatible update (result code: -7).
Cause analysis: The package name of the later version is the same as that of the earlier version currently installed, but their signatures are different.
Solution: Change the signature of the later version to that of the earlier one.
Incompatible app that supports ShareUid (result code: -8).
Cause analysis: The installation failed because the signature of the to-be-installed app that supports ShareUid is different from that of the installed app that supports ShareUid.
Solution: Ensure that the signature is the same as that of the installed app that supports ShareUid.
The shared library is lost (result code: -9).
Cause analysis: The Google Maps library that the app depends on does not exist. As a result, the app installation failed.
Solution: It is recommended that you integrate HMS Core into your app to avoid such dependency issues.
An element name of the to-be-installed app is the same as that of an installed app (result code: -13).
Cause analysis: The ContentProvider defined in the app is the same as that of an installed app.
Perform the following steps to find the conflict:
View logs and check the installation failure callback information.
Run the adb command to obtain all ContentProvider definitions on the device, and find the app that caused the conflict. adb shell dumpsys package providers >d:/temp/provider.txt Solution:Uninstall the conflicting app or resolve the conflict.
The app is incompatible with the CPU of the device (result code: -113 or -16).
Cause analysis: Adaptations for specific CPU versions were not performed when the app was packaged.
Solution: Adapt the app for the CPU version of the device in question.
App verification timed out (result code: -21), and app verification failed (result code: -22).
Cause analysis: When the app was being automatically verified by Google Play, the network connection timed out. Usually, the preceding process is not triggered unless Google Play has been updated by the user or by a downloaded app, which leads to verification timeout.
Solution: On the device, go to Settings > Apps > Google Play Services and tap DISABLE on the App info page, or go to Settings > Apps > Google Play Services Updater and tap Uninstall updates in the upper right corner. Then click FORCE STOP (if available) to deactivate the app if it is still displayed in the app list.
On the device, ensure that Google Play Protect is disabled.
The app package failed to be installed because a later version has been installed (result code: -25).
Cause analysis: Android devices allow for the creation of multiple user accounts. A non-owner account may have downloaded and installed a later version of the app in PrivateSpace for testing purposes. If so, the installation will fail.
Solution: Check whether a later version of the app is installed in PrivateSpace by a non-owner account. If so, uninstall the app and install it again.
Parsing failed (result code: -102).
Cause analysis: An error occurred when generating the package, causing parsing to fail.
Solution: Contact the technical support of the corresponding channel to check logs to locate the download path, download the APK again using a browser, and then install the APK in ADB mode to check whether the error occurs again.
The app package does not contain any certificates (result code: -103).
Cause analysis: The app package is for Early Access targeting specific users and does not contain any certificates.
Solution: Add a certificate to the app package.
Unknown error (result code: -111).
Cause analysis: The device is a TD Tech dual-system policing terminal and is customized to limit app installation.
Solution: Instruct users to contact TD Tech for assistance.