Related
Has anyone had trouble using the 'check for updates' feature on the stock B&N App Library? I have a couple of apps that were purchasedfrom B&N and newer versions are available, but I can't get the updates after rooting. I have tried archiving the apps and reinstalling, but the old version gets reinstalled, not the new version. Any ideas on how to get B&N app updates?
Thanks, William
is it roots fault?
If the apps are really worth it to you, you could always use the acclaim.update method to restore before root and then archive the update apps. Then, when you re-root make sure you don't debloat any of the Nook software (if you debloated the first time). Good luck, see if it works.
landonotis said:
If the apps are really worth it to you, you could always use the acclaim.update method to restore before root and then archive the update apps. Then, when you re-root make sure you don't debloat any of the Nook software (if you debloated the first time). Good luck, see if it works.
Click to expand...
Click to collapse
I used part of your suggestion and found a work around solution. There is no need to unroot the Nook. Simply archive the apps (which uninstalls them) then go back to the B&N app store and un-archive the same apps....it downloads the latest version and installs it. There is one odd thing I discovered.....if you have set a "Password for Purchases" you will have to remove it before it will download the new version.
Thanks for the archive suggestion.
So on my kindle i had everything installed to have the play store working and i got the play store to work and i got the youtube app to work. And so what happened was i deleted the youtube app and installed the newest version and when i opened youtube it gave me the google play services error, but the play store itself still worked.
So what i did was i uninstalled all the google account manager, google services frame work, etc.
And tried to fix the youtube issue by reinstalling all of those things. I started by installing google account manager, and then i rebooted it to install the next thing. Only, when it started up i could unlock the device, but none of the apps would load. So i did a stupid thing and factory reset it, which i think got rid of the root.
I have no idea what to do. I couldn't find any thread about this.
The notificaton bar works and the navigaton buttons show up on the side. So i can get to settings, but the carousel and home screen won't load after i unlock it
here are some pics:
i can't post links because i'm a new member so type it in without spaces
http :// imgur . com / a/ uuB6f
What version of firmware do you use?
ONYXis said:
What version of firmware do you use?
Click to expand...
Click to collapse
13.3.2.6
Sorry, I missed that you did hard reset. without root I think i can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root. Of course if your devices HDX 7.
ONYXis said:
Easiest way , i think, is install safestrap and flash stock firmware by SafeStrap (without wiping anything!)
after that gapps need to install again.
Adb working?
Click to expand...
Click to collapse
How am i going to install safestrap when i can't open any apps?
android2204 said:
How am i going to install safestrap when i can't open any apps?
Click to expand...
Click to collapse
Sorry, I missed that you did hard reset. without root I think you can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root possibility.
What do you mean by loose root possibility?
android2204 said:
Do you mean by loose root possibility?
Click to expand...
Click to collapse
Sorry. English isn't my native language so I don't understand your question.
I wrote that if you upgrade to 13.4.1.1 you will not be able to obtain root.
How do i update?
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
link to update file https://kindle-fire-updates.s3.amazonaws.com/update-kindle-13.4.1.1_user_411009920.bin
Yes. but how would i install it?
you wrote ""So i can get to settings, ", what difficulties after that?
Can you get into Settings - Device - System Updates?
nevermind. so i followed the instructions and put the update into the internal storage folder but when i went into system updates on my kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
android2204 said:
kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
Click to expand...
Click to collapse
Try to turn off wifi and reboot.
You should see that your device has found update, no more variants.
I'll try it again after school. What would I do next if I get the error again?
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
ONYXis said:
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
Click to expand...
Click to collapse
I didn't really understand any of that. What is a broken symlink? And I don't think I'm rooted because I factory reset it.
Also, how could I check root status and what would be the purpose?
Okey. You not rooted now, so do not pay attention.
Your one method to get working device is update firmware.
In way that I described.
If you do not see "update" button after pulling file - sorry. no other idea.
So basically, if this doesn't work I'm screwed?
Anyone else got any ideas?
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
tech_head said:
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
Click to expand...
Click to collapse
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Chilidog said:
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Click to expand...
Click to collapse
Same issue.
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
roirraW "edor" ehT said:
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
Click to expand...
Click to collapse
I may have a build prop file. Somebody will figure it out.
joshua70448 said:
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Click to expand...
Click to collapse
Android pay won't work if you're rooted or if you are using a third party lockscreen.
vv1914 said:
Android pay won't work if you're rooted or if you are using a third party lockscreen.
Click to expand...
Click to collapse
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
tech_head said:
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
Click to expand...
Click to collapse
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Bramton1 said:
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Click to expand...
Click to collapse
Well, that didn't work. New approach, same message.
I wish there was a way we could consolidate our experiences across all devices. It would be helpful to know which devices and ROMs have more success than others. For example, my observation has been that stock ROMs are more successful than custom ROMS like CM 12.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
I tried to add cards before I installed Xposed, even after disabling root via SuperSU it wouldn't work.
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
NedDasty said:
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
Click to expand...
Click to collapse
Tried those running RR. Failed again. Seeing that JasmineROM is a stock rom and RR is a CM-based rom, it supports my beliefe that Android Pay doesn't like CM.
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
I too can confirm Android Pay works on JasmineROM 8!
If I've helped, please don't forget to press the “Thanks” button!?
I read somewhere that it checks the bootloader. I have the "1003" secure boot error and I can't add cards no matter what I do regarding SU. Is this a common thread with everyone here that can't verify? Anyone know how to correct it while running CM12?
csyrell said:
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
Click to expand...
Click to collapse
I'm running Xposed and a new cloak module developed in the last few weeks for Pay.
I also have Tasker set up to enable NFC on Pay opening.
A modified framework (Xposed), root and a ROM not based on stock all cause issues.
BTW: I'm on Jasmine 8.0.
Considering backing up my current configuration, flashing JasmineROM, adding cards, and then restore the backup.
Sent from my LG-VS985 using XDA Premium App
As phone boot up,I just got tons pop-ups of "Google Play Services has stopped working""Google Play Store has stopped working"
MM,with root.
featzhang said:
As phone boot up,I just got tons pop-ups of "Google Play Services has stopped working""Google Play Store has stopped working"
MM,with root.
Click to expand...
Click to collapse
the lack of information makes it really hard to help you in any way.
First of all, there's actually no root for MM.
Dirty or clean flash?
Which version did you flash?
how did you flash it?
toxic_garden said:
the lack of information makes it really hard to help you in any way.
First of all, there's actually no root for MM.
Dirty or clean flash?
Which version did you flash?
how did you flash it?
Click to expand...
Click to collapse
32.1.A.1.163 with flashtool,dirty flash.I get root by flash supersu
featzhang said:
32.1.A.1.163 with flashtool,dirty flash.I get root by flash supersu
Click to expand...
Click to collapse
Are you sure root is working? I'm pretty sure it's not possible yet?
kevinwu128 said:
Are you sure root is working? I'm pretty sure it's not possible yet?
Click to expand...
Click to collapse
I'm sure it's working,get new kernel here and get a twrp with it
toxic_garden said:
the lack of information makes it really hard to help you in any way.
First of all, there's actually no root for MM.
Dirty or clean flash?
Which version did you flash?
how did you flash it?
Click to expand...
Click to collapse
And I get logcat for it.
java.lang.RuntimeException: Unable to create application com.google.android.finsky.FinskyApp: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference
featzhang said:
dirty flash
Click to expand...
Click to collapse
yeah.....no. I know it's pretty convenient to keep all the app- and systemsettings and stuff, but dirty flashing MM over LP is going to mess up your system very likely. Even if you wipe cache and stuff, it just doesn't run any stable at all. So do yourself a favour and install clean.
Also, before installing TWRP and Custom Kernel, you might wanna try if your problem already exists with stock kernel and recovery. I didn't know there was any option for root w/ unlocked bootloader, so i can't say anything about the stablity of it.
toxic_garden said:
yeah.....no. I know it's pretty convenient to keep all the app- and systemsettings and stuff, but dirty flashing MM over LP is going to mess up your system very likely. Even if you wipe cache and stuff, it just doesn't run any stable at all. So do yourself a favour and install clean.
Also, before installing TWRP and Custom Kernel, you might wanna try if your problem already exists with stock kernel and recovery. I didn't know there was any option for root w/ unlocked bootloader, so i can't say anything about the stablity of it.
Click to expand...
Click to collapse
Problem occurs both stock and custom,well I'll try wipe and flash it.
If you haven't wiped yet, try this. I dirty flashed from LP to MM using the FTF and this is how I got the play services to stop asking for an update so it might work for you too.
1) Uninstall updates for Google Play Services and let it revert to the copy in /system
You'll need to make sure you don't have Google Play Services listed as a device administrator first (android device manager, smart lock, Gmail on exchange, etc.)
2) Clear app data for both Google Play Services AND the Play Store app (this is crucial!)
3) Load up Play Store again and let it update Google Play Services.
It may take a few times forcing a Play Services update but it should work.
hipsterfont said:
If you haven't wiped yet, try this. I dirty flashed from LP to MM using the FTF and this is how I got the play services to stop asking for an update so it might work for you too.
1) Uninstall updates for Google Play Services and let it revert to the copy in /system
You'll need to make sure you don't have Google Play Services listed as a device administrator first (android device manager, smart lock, Gmail on exchange, etc.)
2) Clear app data for both Google Play Services AND the Play Store app (this is crucial!)
3) Load up Play Store again and let it update Google Play Services.
It may take a few times forcing a Play Services update but it should work.
Click to expand...
Click to collapse
No luck,still crashing
When I try to install an app it says app not installed. I have tried signing the app, changing the version number and can't get it to work. I have tried installing apks I have downloaded and patched apks from lucky patcher and nothing works. So is there something that doesn't allow the phone to install modified apps?
I can't install samsung keyboard apk on my samsung galaxy s9+
Are you trying to install a new version of an apk that's already on your phone? If so, can you uninstall the older version first?
it is Android 8.0 security features. Google removed install unknown source. You need to give specific permission to file browsers or apps that does the install - for example, if you have app, copy to your phone, and open Samsung File, and click to install.
jazzespresso said:
it is Android 8.0 security features. Google removed install unknown source. You need to give specific permission to file browsers or apps that does the install - for example, if you have app, copy to your phone, and open Samsung File, and click to install.
Click to expand...
Click to collapse
Yeah I did that to allow installs from Samsung file browser and lucky patcher but still not installing. It let's me push the install button and starts the process then says app not installed. I made sure that the previous version is not installed and reset the phone but still not working
Yeah I have allowed installs from the apps I am using to try to install and there isn't a previous version on the phone I made sure to uninstall the app and restart the phone after and still not allowing the install. It starts the install then says app not installed
Echo692 said:
Yeah I have allowed installs from the apps I am using to try to install and there isn't a previous version on the phone I made sure to uninstall the app and restart the phone after and still not allowing the install. It starts the install then says app not installed
Click to expand...
Click to collapse
possibly version of the app (arm/arm64) you are trying...
jazzespresso said:
possibly version of the app (arm/arm64) you are trying...
Click to expand...
Click to collapse
How would I check which it is or change it if need be?
Echo692 said:
How would I check which it is or change it if need be?
Click to expand...
Click to collapse
the app you trying to install, unmodified one, go apkmirror.com and search for it, it should list different version, some apps has arm and arm64 version, download it to your phone, and install it.
your s9/s9+ are arm64
jazzespresso said:
the app you trying to install, unmodified one, go apkmirror.com and search for it, it should list different version, some apps has arm and arm64 version, download it to your phone, and install it.
your s9/s9+ are arm64
Click to expand...
Click to collapse
Ok will try thank you
Hi everybody
The same error (app not installed) occurs when i try to install live message apk or another samsung app, like keyboard, i checked with another files and doenst work
View attachment 4488914
x-geo said:
Hi everybody
The same error (app not installed) occurs when i try to install live message apk or another samsung app, like keyboard, i checked with another files and doenst work
View attachment 4488914
Click to expand...
Click to collapse
Emm nobody?
Samsung blocked sideloading most of it's system apps. Nothing you can really do about it.
Replace app with tutuapp
Your Android application may not be suitable for them. What you need to do now is:
Try updating Android, otherwise you go to the store by reinstalling your device, but this is very time consuming and costly. You can also use tutuapp android (visit tutuappplus.net to download) this free app store that helps me use great apps for Android.