Changed Google Password - now can't use Google apps - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

I changed a google password for an account that is associated on a FireHD 10. (The password change was done on another device). I had previously installed the Google framework and apps using the Amazon Fire Toolbox 6.1. Once the password was changed, the tablet obviously won't connect to the Google servers. The problem lies with the fact that I can't seem to update the Google password on the tablet.
I'm sure a factory reset will work, but I'm trying to avoid the hassle of redoing everything on the tablet. So, other than doing a factory reset, does anyone have a solution that would allow me to reenter the Google password or even remove the Google framework? I was hoping that the toolbox would have a "remove Google" option so I could remove it and then reinstall it, but it doesn't.
Thanks!

I found this in another thread. I'm going to see if it will work....
Datastream33 said:
Firstly, I want to apologize for this frustration and I will give it my all and help you to the best of my ability. Hopefully, we can get this issue resolved. I have a few methods I'd like for you to try if you don't mind. As always, I'm here for you and I'm willing to help to the fullest extent.
Method 1:
Close the Play Store.
Clear it from the recents.
Turn off the WIFI for the device.
Clear the cache for the Play Store, Framework, Account Manager, and Play Services.
Remove your google account if its already been added.
Open the Play Store, it will tell you that you aren't connected.
Keep the Play Store open and turn on the WIFI.
Attempt to sign in again.
Method 2:
Plug your device into your computer and open up Toolbox V6.3
Click on the ADB Shells tool and execute a Standard Shell.
Execute these commands:
Code:
pm uninstall com.google.android.gsf.login
Code:
pm uninstall com.google.android.gsf
Code:
pm uninstall com.google.android.gms
Code:
pm uninstall com.android.vending
Once complete close out of the shell and reopen the Toolbox.
Execute the Install Google Services tool and wait for the process to complete.
Once the tool finishes please wait for a few minutes for the Play Store to update itself.
Open the Play Store and attempt to sign in.
Please let me know if you need further help. Best of luck!
Click to expand...
Click to collapse

Related

Can't use Google Play Store, help me please

I just update to Android 5.0
When i enter Google Play it says i have to do an Obligatory Autentication ( I mean Autenticacion Obligatoria) and it doiesn't let me donwload anything, also when sync my Google Account it says it has some incidences, also i can't erase my Google account because i don't have permission. Also it says in a Notification that an App neds to be updated by Google Play services but i csn't because i can't enter Google Play.
It seems like they shouldn't release Lollipop at least for Nexis 4
aloarayacr said:
I just update to Android 5.0
When i enter Google Play it says i have to do an Obligatory Autentication ( I mean Autenticacion Obligatoria) and it doiesn't let me donwload anything, also when sync my Google Account it says it has some incidences, also i can't erase my Google account because i don't have permission. Also it says in a Notification that an App neds to be updated by Google Play services but i csn't because i can't enter Google Play.
It seems like they shouldn't release Lollipop at least for Nexis 4
Click to expand...
Click to collapse
If you already have a google account and its misbehaving, either do a factory reset and set up your phone again. Or try adding a second google account and then erase the original account. The Google playservices notification is a bit of a bug, try downloading the latest apk from apkmirror and install it.
Ok, but the think is that i can erase or add a Google account, when i try to erase it it says that Device Manager is active, i try to deactivate it but nothing, also i downloaded the apk but when i try to open it it says error
Also i want to do a factory reset but i have more than 1000 songs i don't mind about other things, i just want to save my songs, but when i connect to my computer with Windows 8.1 it detects the Nexus but i can't see the files, it doesnt prompt anything.
aloarayacr said:
Ok, but the think is that i can erase or add a Google account, when i try to erase it it says that Device Manager is active, i try to deactivate it but nothing, also i downloaded the apk but when i try to open it it says error
Also i want to do a factory reset but i have more than 1000 songs i don't mind about other things, i just want to save my songs, but when i connect to my computer with Windows 8.1 it detects the Nexus but i can't see the files, it doesnt prompt anything.
Click to expand...
Click to collapse
Check in Device Manager on your PC, if the phone shows up as an Unknown Device, you need to install/ reinstall the usb drivers. For windows 8.1 try the Universal ADB drivers (google for the link).
The solution to all Lollipop bugs is to uninstall Google Services and then reinstall and updated apk, i was plagued with all of this bugs, i managed to deactivate Android Device Manager and i uninstall Google Services, all of my Google Apps were gone it was pretty weird so i install a Google Services apk and now its smooth as f-word, i will never buy a Nexus cause of this but if all updates were as fluid as know i would love all of this but i had many headaches because of all the trouble that updating cause to my N4.
Had a similar issue with the OTA update this morning. You need to get the latest version of the Google Play Services apk. Check this thread for the download link posted by Hashim. You need to check the correct version for your phone. Its a 30 mb file and takes around 20-30 min to install. All the bugs you mentioned were fixed on my phone.
https://productforums.google.com/fo...ce=footer#!msg/nexus/hfEp9s5vxhI/vPe8KbTcob0J

Working Playstore

Finally solved and working. I've tested almost all Google Apps and they work, including hangouts. The device used is a Amazon Fire HD 6.
Files needed for this process can be found here. Download these to your device prior to starting the guide. Also download "ES File Explorer" free from the Amazon Appstore, and ensure Root Explorer is enabled in the options.
Obtain root here.
Change over to SuperSU and install busybox following this guide.
Disconnect WiFi
Install all five APK files you download before starting this guide. Do not open them yet.
Run SystemAppMover and convert Google Account Manager, Google Playstore, Google Services Framework, and Google play services into system apps. (The key to this step is to make sure that the apps are in "\system\priv-app" directory. When I was using Titanium Backup, or "otherways" to convert them to system apps they were being moved to the "\system\app" directory. They MUST be in the "\system\priv-app" folder to function correctly)
Reboot
Run ES File Explorer and navigate to the "\data\app" directory. Create 4 directories named
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
Select each folder, press more in the bottom right corner and choose properties. Click the change button next to permissions, uncheck all checkmarks and hit OK. Doing this will prevent any of these APK from updating.
Re-enable wifi, and enjoy.
The road to victory...
FINAL UPDATE: Solved by moving the 4 google APK files from \system\app folder to the \system\priv-app folder. YUP, that simple. Installing as just as system app wasn't granting enough permissions I don't think. Will update and clean up guide, thanks again to everyone for help on this one!
UPDATE #5: 5/22/2015 0035 CST: I was really trying to avoid this but I'm going to factory reset and start all over, no matter what I do now I just get force closes. From what I can tell in Logcat it looks like a problem with the download manager? If anyone has more insight into the logcat please PM me or post. Hopefully this weekend I'll have the time needed to spend doing this.
UPDATE #4: 5/19/2015 0759 CST: Still more of the same force closing and sporadic unstable behavior. I've tried version of Play services from 6.5.99- current all with the same results. I've tried multiple versions of the play store as well all the way back into the 4.X.XX. The only thing that ever gets me close seems to be wiping the cache of play services and store. I usually can at least begin to download something before I force close. I've started removing other variables apps as well but nothing seems to help. This is all happening before services does its auto background update, so I dont think it's that problem. I've used 034 and 070 versions of services both having the same results. Will keep testing as time allows. I'm using an Amazon Fire HD 6. Two people have confirmed working on HD 7's, waiting on versions they have been successful with.
UPDATE #3: 5/17/2015 2214 CST: Still having issues with random force closes. When wiping the cache for the playstore and Google Services it seems that it will work for a short time, and then after closing will go right back to a force close. I'm going to try to upgrading services to a slightly newer build and freeze it from updates (although that has not yet caused the problem we seem to be facing). If this does not work I will try rolling the store version back and see if it can be frozen from updates. I'm at work now so hopefully I'll have a chance to do some testing early morning - tomorrow afternoon.
UPDATE #2: 5/17/2015 1624 CST: Problem seems to lie in Google Play Services Auto Updating. Use Version 6.5.99 provided by @powerpoint45 in his GAPPS tutorial. I first converted the new on to a user app, uninstalled it, reinstalled his 6.5.99 version converted it back to system app and changed permissions on the new install:
Code:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
These are the versions I am using and everything is working fine so far:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will thoroughly test it this time, and if all is well I will condense and clean this guide up.
UPDATE #1: 5/17/2015 1525 CST: This worked 100% before I went to bed, I woke up and tried to launch playstore and it is sitting at a white screen. I think it has something to do with something updating I am working on fixing it now. I will post updates here, as I solve this.
Here we go, 100% Playstore functionality as far as I've tested so far.
Installed powerpoint45's second GAPPS package as outlined in his thread about installing GAPPS.
I'm no expert but I think the important step here is changing the permissions via ADB as described in his post.
Used Kingroot to root as outlined in the rooting instructions post.
Changed over to SuperSU following this guide.
After obtaining root I used an App called System App Converter (I'm sure there are many other ways to do this) and changed the following apps to system apps:
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Playstore seems to function just fine for me now! Yay!
Other possible variables to getting this to work:
I have the following 2 packages blocked via ADB (This will stop OTA)
com.amazon.otaverifier
com.amazon.dcp
:highfive::good::fingers-crossed:
Hope this keeps working and helps someone else get this working! Thanks to everyone who got us this far!
Do uknow how to block the ad and **** that pop up when using this tablet out of the blue on the bottom or middle sometimes ??
AlbusAngelus said:
Here we go, 100% Playstore functionality as far as I've tested so far.
Installed powerpoint45's second GAPPS package as outlined in his thread about installing GAPPS.
I'm no expert but I think the important step here is changing the permissions via ADB as described in his post.
Used Kingroot to root as outlined in the rooting instructions post.
Changed over to SuperSU following this guide.
After obtaining root I used an App called System App Converter (I'm sure there are many other ways to do this) and changed the following apps to system apps:
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Playstore seems to function just fine for me now! Yay!
Other possible variables to getting this to work:
I have the following 2 packages blocked via ADB
com.amazon.otaverifier
com.amazon.dcp
:highfive::good::fingers-crossed:
Hope this keeps working and helps someone else get this working! Thanks to everyone who got us this far!
Click to expand...
Click to collapse
so i did this and set
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
to system apps rebooted on each one went to open playstore got white screen and loading circle nothing else.
---------- Post added at 07:13 PM ---------- Previous post was at 07:01 PM ----------
whats the command to do this via adb
I have the following 2 packages blocked via ADB
com.amazon.otaverifier
com.amazon.dcp
AlbusAngelus said:
Here we go, 100% Playstore functionality as far as I've tested so far.
Installed powerpoint45's second GAPPS package as outlined in his thread about installing GAPPS.
I'm no expert but I think the important step here is changing the permissions via ADB as described in his post.
Used Kingroot to root as outlined in the rooting instructions post.
Changed over to SuperSU following this guide.
After obtaining root I used an App called System App Converter (I'm sure there are many other ways to do this) and changed the following apps to system apps:
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Playstore seems to function just fine for me now! Yay!
Other possible variables to getting this to work:
I have the following 2 packages blocked via ADB
com.amazon.otaverifier
com.amazon.dcp
:highfive::good::fingers-crossed:
Hope this keeps working and helps someone else get this working! Thanks to everyone who got us this far!
Click to expand...
Click to collapse
Thanks! I neglectecd to make play store a system app, that fixed my downloading errors.
s1urpee said:
Do uknow how to block the ad and **** that pop up when using this tablet out of the blue on the bottom or middle sometimes ??
Click to expand...
Click to collapse
From adb:
Check devices:
adb devices
Go to shell
adb shell
Disable Ads:
pm block com.amazon.kindle.kso
AlbusAngelus said:
Here we go, 100% Playstore functionality as far as I've tested so far.
Playstore seems to function just fine for me now! Yay!
Click to expand...
Click to collapse
Yay, for sure! Thanks a lot. Could you please add how you blocked OTA updates after rooting? That would make your post the go-to one for getting this job done.
EDIT: Oh, now I see it down at the bottom! ok.
s1urpee said:
so i did this and set
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
to system apps rebooted on each one went to open playstore got white screen and loading circle nothing else.
Click to expand...
Click to collapse
Have you followed the installing GAPPS guide at the top of the post and used ADB to change the permissions as outlined by Powerpoint45? That I think is an important step in this process.
EDIT: Having same problem now, working on a solution, watch OP.
One fix for white screen with Play Store
s1urpee said:
so i did this and set
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
to system apps rebooted on each one went to open playstore got white screen and loading circle nothing else.
Click to expand...
Click to collapse
This happens also on 2013 Kindle Fire HD and other devices running Fire OS 4.x.x. We fixed it by downgrading Play Services and preventing it from updating. Here's the method we used.
- You need Busybox Pro. May want a terminal emulator
- This assumes com.google.android.gms-1.apk is in /data/app​
1. Install Busybox Pro (needed for the chattr command)
2. Go to APKMirror site and download an older version of Google Play Services, but DON'T INSTALL IT YET.
I'm using v. 7.0.96". It's from March but current Play Store and all google apps work with it, and you can try a later version, uh, later.
For 2013 7" HD the apk is com.google.android.gms-7.0.96_(1785884-034)-7096034-minAPI9.apk. Note: The 3 numbers after the dash (1785884-nnn) matter. Read the info at APKmirror to choose the right one.​3. Turn off wifi
4. Uninstall the Play Services update (may need to use file explorer)
5. Install the older Play Services you got.
6. Make sure you have /data/app/com.google.android.gms-1.apk, not gms-2
7. On terminal emulator or from a cmd window run:
Code:
adb shell
su
touch /data/app/com.google.android.gms-1.apk
chattr +i /data/app/com.google.android.gms-1.apk
The +i (immutable) prevents any changes. Use -i to reverse.​8. Turn on wifi and try play store. Reboot and recheck that it's okay.
If still problem with play store, get Play Store 5.4.1.0 from APKMirror and install. It will update to the current version (5.4.1.2) and then work.​.
Not working for me either ...
I've matched the google apk versions, converted to system with Titanium Backup, and still end up with the white screen. Youtube works, so the permissions are fine.
So far there only seems to be 1 person able to get Playstore to work (the original poster).
DoLooper said:
This happens also on 2013 Kindle Fire HD and other devices running Fire OS 4.x.x. We fixed it by downgrading Play Services and preventing it from updating.
EDIT 5/17/2015: I see OP has apparently resolved the problem, but maybe this can still help you or others. - You need Busybox Pro. May want a terminal emulator
- This assumes com.google.android.gms-1.apk is in /data/app​
1. Install Busybox Pro (needed for the chattr command)
2. Go to APKMirror site and download an older version of Google Play Services, but DON'T INSTALL IT YET.
I'm using v. 7.0.96". It's from March but current Play Store and all google apps work with it, and you can try a later version, uh, later.
For 2013 7" HD the apk is com.google.android.gms-7.0.96_(1785884-034)-7096034-minAPI9.apk. Note: The 3 numbers after the dash (034) matter. Read the info at APKmirror to choose the right one.​3. Turn off wifi
4. Uninstall the Play Services update (may need to use file explorer)
5. Install the older Play Services you got.
6. Make sure you have /data/app/com.google.android.gms-1.apk, not gms-2
7. On terminal emulator or from a cmd window run:
Code:
adb shell
su
chattr +i /data/app/com.google.android.gms-1.apk
The +i (immutable) prevents any changes. Use -i to reverse.​8. Turn on wifi and try play store. Reboot and recheck that it's okay.
If still problem with play store, get Play Store 5.4.1.0 from APKMirror and install. It will update to the current version and then work.​.
Click to expand...
Click to collapse
Well, I've temporarily resolved the problem, upon coming home from a run after everything working and in order, the play store started to force close everytime I tried to open it. Nothing had updated yet and I didn't do anything on the tablet so I'm assuming something happened in the background. I'm going to try your method or freezing the updates to services (although version numbers matched when I came back) and see what the result is. Also I'm going to try to roll back the playstore. So you know if it would be possible to freeze it as well? Upon clearing services catch the playstore then opened and shortly forced closed after. So what ever the issue is seems to have something to do with what's being written to the cache.
bibikalka said:
Not working for me either ...
I've matched the google apk versions, converted to system with Titanium Backup, and still end up with the white screen. Youtube works, so the permissions are fine.
So far there only seems to be 1 person able to get Playstore to work (the original poster).
Click to expand...
Click to collapse
See above and watch the updates. It is still not working without issues. It seems to work for a while then it sits I come back and it's acting funny one way or another. I'm going to keep working on this.
AlbusAngelus said:
Well, I've temporarily resolved the problem, upon coming home from a run after everything working and in order, the play store started to force close everytime I tried to open it. Nothing had updated yet and I didn't do anything on the tablet so I'm assuming something happened in the background. I'm going to try your method or freezing the updates to services (although version numbers matched when I came back) and see what the result is. Also I'm going to try to roll back the playstore. So you know if it would be possible to freeze it as well? Upon clearing services catch the playstore then opened and shortly forced closed after. So what ever the issue is seems to have something to do with what's being written to the cache..
Click to expand...
Click to collapse
Sorry, I haven't tried freezing so can't say. Seems like that would disable it, and google could still install an update. Anyway, the commands were used throughout the KFSOWI community, and Play Store and all current versions of google apps--gmail, g+, hangouts--have been working fine for several weeks. As I remember, though, I had to open and close some a few times to get past an error saying something like "requires play services update." Anyway, worked a treat!
Caveats: Not sure I'm using same version of google services framework as you, if that would matter. (I'll check shortly.) Also be sure you get the right play services for your device based on those 3 numbers.
EDIT: My Google Services Framework=4.4.4, FWIW.
Couple other thoughts...Play Store rollback sounds like good plan. Maybe Services 6.5.99 just doesn't support current version(?) Also, if you really want to stay on services 6.5.99, you could turn off wifi, move everything back to data and run the following commands, which creates a fake update file and prevents access. (Need ROM toolbox pro)
adb shell
su
touch /data/app/com.google.android.gms-1.apk
chattr +i /data/app/com.google.android.gms-1.apk
DoLooper said:
Sorry, I haven't tried freezing so can't say. Seems like that would disable it, and google could still install an update. Anyway, the commands were used throughout the KFSOWI community, and Play Store and all current versions of google apps--gmail, g+, hangouts--have been working fine for several weeks. As I remember, though, I had to open and close some a few times to get past an error saying something like "requires play services update." Anyway, worked a treat!
Caveats: Not sure I'm using same version of google services framework as you, if that would matter. (I'll check shortly.) Also be sure you get the right play services for your device based on those 3 numbers.
EDIT: Google Services Framework=4.4.4, FWIW.
Couple other thoughts...Play Store rollback sounds like good plan. Maybe Services 6.5.99 just doesn't support current version(?) Also, if you really want to stay on services 6.5.99, you could turn off wifi, move everything back to data and run the following commands, which creates a fake update file and prevents access. (Need ROM toolbox pro)
adb shell
su
touch /data/app/com.google.android.gms-1.apk
chattr +i /data/app/com.google.android.gms-1.apk
Click to expand...
Click to collapse
Great thoughts exactly what I was thinking in your edit. The fact it's opening then just force closing is making me think that for some reason that version of services is not compatible with the newer version of the store. I Think what I will try to do is first use a newer version of services and freeze it to see if that resolves it If that doesn't work I'm going to try to roll back services and the store and freeze them both. Feel like it's something trivial at this point. Having the newer versions may help keep things compatible longer.
s1urpee said:
whats the command to do this via adb
I have the following 2 packages blocked via ADB
com.amazon.otaverifier
com.amazon.dcp
Click to expand...
Click to collapse
I missed this question somehow, and you've probably figured it out by now but just in case it is:
Code:
adb shell
pm block com.amazon.otaverifier
pm block com.amazon.dcp
Do anyone have the drivers I need to install to use ADB on the Fire HD 7? I know I can DL them from the Android SDK pack but I'd rather not go through all of that if I don't have to.
DoLooper said:
EDIT: My Google Services Framework=4.4.4, FWIW.
Click to expand...
Click to collapse
Do you know where I can get this version, I fear that this maybe causing an issue as well. So far I'm still having force closes that can almost always be solved by wiping store data and sometimes Google play services. I've tried various combos of play store and playstore services. I did an oopsie in frustration and wiped the framework but after doing a bit of reading I certainly having at least 4.4.2 would be ideal.
dont suppose ya know how to stop the ads that popup when using the tablet do ya ?
---------- Post added at 03:39 PM ---------- Previous post was at 03:35 PM ----------
tried Google Services Framework=4.4.4 and now i'm back to check your connection and try again google play msg
So i managed to get my playstore to load and download games just fine and rebooted a few times and still works fine. atm
framework services 4.4.4 playstore is 5.4.12 and services running 7.0.96 1785884-034
4.4.4 framework
AlbusAngelus said:
Do you know where I can get this version, I fear that this maybe causing an issue as well. So far I'm still having force closes that can almost always be solved by wiping store data and sometimes Google play services. I've tried various combos of play store and playstore services. I did an oopsie in frustration and wiped the framework but after doing a bit of reading I certainly having at least 4.4.2 would be ideal.
Click to expand...
Click to collapse
Here's a place to get 4.4.4 and a discussion of installing: http://forum.xda-developers.com/showthread.php?t=1482894
---------- Post added at 10:33 AM ---------- Previous post was at 10:23 AM ----------
s1urpee said:
framework services 4.4.4 playstore is 5.4.12 and services running 7.0.96 1785884-034
Click to expand...
Click to collapse
Not sure I follow. Do you mean you're using these framework, playstore and play services versions? Did you run commands I posted to prevent play services from updating? Thanks.
.
---------- Post added at 10:38 AM ---------- Previous post was at 10:33 AM ----------
argrr101 said:
Do anyone have the drivers I need to install to use ADB on the Fire HD 7? I know I can DL them from the Android SDK pack but I'd rather not go through all of that if I don't have to.
Click to expand...
Click to collapse
Just google "xda install adb"
In order to prevent Apps installed trough Playstore, just uncheck the "Auto Update" if you click the top right corner at the Google Playstore and also go to settings (Swipe from left to right) and select "Automatic App-Updates" from General tab and disable them.
I'm currently using:
Root with Kingsroot - SU sideloaded
Google Play Store 5.5.8
Google Play Services: 7.0.99 (1809214-034)
Google Play Framwork: 4.0.4-338691
All Apps working (Adsense, Hangouts, Google Search, Calendar etc.)
I also installed Cyanogenmod (11) the HDX (3rd gen) installs successfully, but it laggs badly so it's not that controlable. Had to reset it, maybe it's a hind to play around with those Kernels
Greetings
vismxownz said:
In order to prevent Apps installed trough Playstore, just uncheck the "Auto Update" if you click the top right corner at the Google Playstore and also go to settings (Swipe from left to right) and select "Automatic App-Updates" from General tab and disable them.
Click to expand...
Click to collapse
Hi . . . It's not the app updates that are causing the problem, it's play services updating from the version installed by the gaaps package they are using. What gaaps did you install? How long has it been working for you? Thanks.

Disable OTA - Keep SDCard Write Access and Use a Different Launcher *READ BEFORE BOOT

Since root has been obtained and an alternative launcher can be installed, as has been mentioned there is really no need to stay on 5.0.0 anymore. I would recommend updating to 5.0.1. However, this procedure can still be applied to 5.0.1 and hopefully it'll prevent any future updates. (As of writing it 5.0.1 is the latest).
The steps are basically as follows:
Enable ADB by going to Settings> Device Options. Keep tapping on the Serial Number field until the Developer options field appears.
Under Developer options Enable ADB
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
I don't know which of three is the magic one, But you can not longer go to device options > system update. It also never appears to pull down the update in the background.
Rivethread23 - good work and many thanks for this
I know that you have the original Fire 7 with no system update but I wanted to see if any of your commands will work on 5.01. My device is on 5.01 has been in aeroplane mode since purchase, I have been using OTG Ethernet for connectivity and I have not signed into Amazon. Google Play is installed - basically a standalone device on 5.01 with no association with Amazon.
After running the commands and the ADB shell gave a [True State] after each command. Rebooted the device:
System Updates now gives the following error message: [The requested action is not permitted. Check Parental controls settings and try again]. As my device is not associated with Amazon parental controls have not been configured - so I browsed to a few proxy sites and such to confirm no filtering on web browsing etc
I've tried various launchers from Play store and every time the default Fire Launcher kicks back in again.
SD Card issue is still there.
When you tried the System Update button did you get the same error message as me? If so, I wonder if the Adb Shell command to disable OTA works on 5.01 as well?
Update 1: [adb shell pm hide com.amazon.firelauncher] disables the default Amazon launcher. I picked another launcher at random from Google Play. Halo installed and it worked with the default launcher hidden, however using the minimise middle button on the device forces the Parental Control Popup to appear.
So it is possible to hide the default launcher on 5.01 using ADB but it is causing issues. We need a better work around.
Unfortunately this only blocks the update from occurring. I ran into another issue on the 5.0.0 tablet in that I can't get Google play store working. It just says cannot connect. So I don't know if one of the above things broke it. It was getting late so I went to bed. I'll keep plugging at it and see what I can do.
I might finally take both of mine out of the box today, can more people confirm this is working? @Rivethread23, did you get the play store sorted out?
Couldn't wait, dove in. On an out-of-box Fire, running 5.0.0, these do in-fact keep the OTA updates from firing. I have been online, installing apps and customizing the tablet for over an hour with many reboots, no prompts or attempts of an update.
With this, and ads disabled, and the play store turned on we have a usable tablet!
F-Droid works as well, just sideload their APK to get access to lots of software:
https://f-droid.org/repo/org.fdroid.fdroid_96150.apk
Still stuck on Play Store in 5.0.0 *not working* for now.....same problem as OP
I can confirm that the Google Play Services, Login Services, and Framework are (at least partly) working, even though the Play Store is not. I sideloaded Gmail, and it automatically had my info, and downloaded my email.
Wait, I'm confused. In 1 post you say play store is on and working, then you're saying it's not...
Aside from the play store, it sounds like everything else is working fine! Is that correct. I'm asking because I'm thinking about buying a 2nd one of these, only if I can have it working 100% the way I have it now with my tablet, just with the ability to use a different launcher.
With the original 5.0.0 firmware, if you prevented the OTA update to 5.0.1:
+Can change launcher
+Can write to SD from apps
-Can't get Play Store to work (so far, but can manually side-load GApps (Gmail, Hangouts, etc))
In the other thread, people that have gone to 5.0.1:
-Locked to amazon Launcher when using HOME button
-Manual SD writing is disabled
+Google Play Store can be installed and 90% of the GApps work
--------
The key to take away is that if you get another one, and you do the fix in this thread to prevent OTA updates, you can simply wait til everyone gets things fixed and figured out. You can safely use it and not worry about getting pushed to a firmware that might be even more locked down.
On the other hand, if you're not worried about OTA updates breaking stuff, and want a working store, go to 5.0.1 and follow SD_Shadow's instructions in his thread on that subject.
Hopefully root comes soon and we can fix all these problems properly, but until then it's kinda hit and miss depending on what version you got.
Hope that helps.
Thanks Tufkal was going to post something along those lines but you beat me to it.
Essentially you can prevent updates from further locking down the tablet. Who knows what future updates bring? I'll wait and update as thing warrant.
I have two one on 5.0.0 and another on 5.0.1. While I like being able to use the launcher of my choosing on 5.0.0, the working google store and updated amazon store and apps have me using the 5.0.1 one. I am keeping the other on 5.0.0 until development starts then I'll try my hand at making a ROM.
Your device that is on 5.0.0 Firmware have you signed into Amazon and associated your device? Or is it standalone like mine?
Was on Amazon for a day. Factory reset it and am using it sans Amazon. Mostly using the 5.0.1 one myself.
Yep same here. 5.01 with no amazon sign in.
I've been playing around with the launcher again. Tried changing the hardcoded buttons and also with ADB Shell am force-stop pm disable on com.amazon.firelauncher to stop dependent services, ie hard buttons. All to no avail.
root definitely needed for this
I figured out a way to access some hidden functions within the OS last night. Seeing where this leads after work today Apparently I can cast the screen and access the home function disabled in 5.0.1. Problem is the home function doesn't override the hard coding.
Most interesting is something called Prod and Devo Switch that give "Access Denied" when I try to activate it. Hmmmm........
Here's what I have discovered. It's easier done on 5.0.0 but can be done on 5.0.1. You'll need another launcher like Nova installed. Installed "Anycut" from the google store. It'll let you put a shortcut on the desktop for any "activity". There are alot of items there not normally accessible. You can cast to a Chromcast for example (it works). The reason you need another launcher is the Amazon launcher doesn't support shortcuts I guess as they don't appear. They appear on Nova's desktop when created.
Most interesting is a shortcut called "Prod and Devo Switch" which if you look at the info refers to the "Amazon Device Settings" app.. ( com.amazon.device.settings?). It's separate from the user settings. If you try to access it it will say "Access Denied" on 5.0.1. Or "Permission denied" on 5.0.0. Makes me wonder if what needs to happen the app needs some additional permissions to be run. I was looking through the list of permissions via ADB and there are a number of permission groups that are android.xxxxx. However there are only a few permission groups that are amazon.xxxxx one of which is amazon.permission-group.settings. Listing the settings in the group shows a large list. Maybe using ADB pm grant com.amazon.device.settings the correct permissions could unlock this? Thoughts?
Here's what I got from a logcat when I click on the shortcut in novalauncher:
I/ActivityManager( 454): START u0 {act=android.intent.action.VIEW flg=0x1000000
0 cmp=com.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310]
} from uid 10017 on display 0
W/ActivityManager( 454): Permission Denial: starting Intent { act=android.inten
t.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoProdConfigActiv
ity bnds=[300,168][400,310] } from ProcessRecord{9460965 1138:com.teslacoilsw.la
uncher/u0a17} (pid=1138, uid=10017) requires com.amazon.dcp.permission.DISPLAY_D
EBUG_UI
E/Launcher( 1138): Launcher does not have the permission to launch Intent { act=
android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoPr
odConfigActivity bnds=[300,168][400,310] }. Make sure to create a MAIN intent-fi
lter for the corresponding activity or use the exported attribute for this activ
ity. tag=ShortcutInfo(title=Prod and Devo Switch intent=#Intent;launchFlags=0x10
000000;component=com.amazon.device.settings/.DevoProdConfigActivity;sourceBounds
=300%20168%20400%20310;end id=15 type=Shortcut container=-100 screen=1 rank=-1 c
ellX=3.0 cellY=1.0 spanX=1.0 spanY=1.0 dropPos=null user=UserHandle{0} modelGene
ration=-1) intent=Intent { act=android.intent.action.VIEW flg=0x10000000 cmp=com
.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310] }
E/Launcher( 1138): java.lang.SecurityException: Permission Denial: starting Inte
nt { act=android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.setting
s/.DevoProdConfigActivity bnds=[300,168][400,310] } from ProcessRecord{9460965 1
138:com.teslacoilsw.launcher/u0a17} (pid=1138, uid=10017) requires com.amazon.dc
p.permission.DISPLAY_DEBUG_UI
Tried granting that specific permission to Nova launcher or the Fire launcher but both do the same thing:
com.amazon.firelauncher com.amazon.dcp.permission.DISPLAY_DEBUG_UI <
Operation not allowed: java.lang.SecurityException: Package com.amazon.firelaunc
her has not requested permission com.amazon.dcp.permission.DISPLAY_DEBUG_UI
Maybe someone with more knowledge than I create a program with that permission that calls the intent in question?
Again good work on this
I picked up another new device yesterday morning. OTA updates disabled, Fire OS 5.0, no association to Amazon and connectivity via WiFi. Just like you I got Gmail, YouTube and other Google associated apps to work with the exception of the Play store. It finally let me sign in but comes up every time with the [Connection Retry] error.
I followed your instructions and installed AnyCut - and I have been playing around as I thought it might be possible by using shortcuts to load my Google account onto the device.
Shortcut [Add an account] - and the "Couldn't sign in - google server error" came back so not working for now.
Shortcut [Testing] - allows us to pull up more info on the Fire 7 with the 4 below options
Tablet Information - not working
Battery Information - working
Usage Statistics - working
WiFi Information - working
Shortcut [IP Settings] - gives us advanced WiFi options
A lot of the options try to load or there is a visible presence of starting to load and you can clearly see the device stopping them from loading. Basically we are trying to load Android Apps that are locked down by Fire OS which sits on top of Android.
Other apps with Permission Denied
[Log Manager]
[Crash Manager]
[Metrics Debug UI]
Looks like Amazon do not want us to have access to their inbuilt log files on their device
As I do not have access to Google store I have been using F-Droid for my apps. I have installed APK Extractor and it lists all the current APK's on the Fire 7. What is interesting about this is that there are APK's that where not findable using [AnyCut] but show up in APK Extractor.
Will update more in a bit
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
tufkal said:
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
Click to expand...
Click to collapse
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
k3ll0gs said:
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
Click to expand...
Click to collapse
I'm trying all kinds, the one i was using for that test I got here:
https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
I'm with you I tried some work arounds on the 5.0.1 tablet but if we can get the play store working on 5.0.0 it seems to offer more opportunities.
Yep same here - it makes more sense to get Play store to work.
I think I might know what the issue is causing and I believe it is down to the Google Service Framework (GSF) on 5.0 not installing correctly and causing the sync issue when trying to connect. I installed [Device ID] app on 5.0 and there is no serial listed for GSF at all - on my 5.1 tablet GSF would load up on the screen and you could view settings but on 5.0 it does not.
When trying to open the Google Play some I found the following error in Logcat [.onClick: b/5160617: Reinitialize account] this relates to the GSF serial not being present. Logs also show permissions and api errors as well. The only
Looking into a GSF workaround if possible. It might be on the wrong track but I am going to see what else I can find out.
I thought I had found a back door into Google signin. Using an App calling [Applications Info] which I used to pull up the GoogleServiceFframework apk. From there I started to play around with the launch options for the applicable services.
Selecting launch on [Legal Services] takes you to Google Sign In - keyboard was not working for this so I had to adb shell input text of my gmail & password. Unfortunately the same old Google error was appearing even after I cleared the cache and re-installed Gapps.
The last screengrab shows that the System Updates on installed Google Service Framework is corrupt and not working properly. I have also launched other Gapps dependent activities from the services in [App Info] and again they either fail to load of abundance of errors. So installation issues for all of the Gapps in one way or another on Fire 5.0
Obviously there is a difference between the 5.0 Rom + 5.01 Rom that is stopping Gapps from working. Due to the amount of errors in Logcat and in Application Info and dependent services not working. My gut is saying that when we have root on 5.0 we have a better chance of getting Gapps working as we will have the ability to play around with not only System files but System commands too.
If anyone has any ideas or what else we could try please chip in.
rivethead23 said:
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
Click to expand...
Click to collapse
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
redst said:
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
Click to expand...
Click to collapse
yes updates would be blocked until you run the unhide commands.
Sent from my KFFOWI using Tapatalk

How can I uninstall Google Play services from Fire HD 10?

I'm having some kind of issue where I'm getting constant error messages saying there was trouble signing into my Google account, but logging out of my Google account, and even removing the Fire under Google security settings doesn't work, so I think I want to just wipe everything Google-related and reinstall them all over again. I've successfully uninstalled everything else, but the "uninstall" button is grayed out for the Google Play services. Any ideas? It is rooted, if that helps.
try uninstalling from a root shell or an package uninstaller app that has root access.
Just disable the device administrator
AmznUser444 Dev said:
Just disable the device administrator
Click to expand...
Click to collapse
THANK YOU! This totally worked.
How do I disable the device administrator? Is this a system setting? I can't find it...
---------- Post added at 05:44 PM ---------- Previous post was at 05:38 PM ----------
Found it: Settings > Security & Privacy > Device Administrator.
There I just disabled all that could be disable and that allowed me to uninstall GPS.
I still can't see the option to remove it from my device admin please help me
Same issue for me.
I installed using the kindle fire toolbox and then, foolishly, uninstalled from the launcher. But this only uninstalls for the current user, then it is gone for this user but still on the device. I can't uninstall "for all users" because it says it is a device admin. I can't remove the device admin because Play Services doesn't appear. The toolbox uninstall says you need to disable the device admin and then loads the admin screen which doesn't show it.
Very frustrating. Serious regrets getting this stupid device!!
Launcher fix
All you need to do is make a user account, then open settings. Click "Apps and Notifications". then click show system apps. Delete all google services, but start with Google Framework Services.

[solved] Google Play Store uninstalled, now cannot get it back

tl;dr: I uninstalled com.android.vending via adb, now re-installing it from APK isn't bringing the icon, or the functionality, back.
So today I tried to use my phone as you do, and "Application Google Play Services has stopped" was popping constantly, stacking the messages one after another, making it hard to even browse through GUI. Restart or clearing app data and app caches didn't helped. So I connected it to PC, and did:
```
adb shell
su
pm disable com.google.android.gms
```
(note: I should've tried "safe mode". But I didn't, so I don't know if it would help.)
The service disable command stopped the errors, but nothing else worked - Google Maps, GMail, even contacts stopped showing - looks like they had no proper local copy (which is concerning as well, but not really the issue I'm trying to solve).
So keeping GMS disabled is not really an option. I tried installing version 21.something and 19.something via adb, these both were constantly crashing as well. I finally went down to `com.google.android.gms_18.7.19` and that one seem to be working. But before that, I started removing services which use GMS - as I assumed the crash is probably caused not by GMS just existing, but by being used incorrectly by other things. One of the removed ones was Play Store - I did:
```
adb shell pm uninstall --user 0 com.android.vending
```
Ok, so no play store. But no problem, it can be easily re-installed from apk, right? Well no. This is the issue.
I tried installing a lot of various versions, but the store just isn't popping in the menu, nor in the activities handlers:
```
# adb shell monkey -p com.android.vending 1
** No activities found to run, monkey aborted.
# adb shell am start -n com.android.vending/com.google.android.vending.activities.MainActivity
Starting: Intent { cmp=com.android.vending/com.google.android.vending.activities.MainActivity }
Error type 3
Error: Activity class {com.android.vending/com.google.android.vending.activities.MainActivity} does not exist.
```
In the "Settings" -> "Applications", the Play Store is on the list, but it is marked as "not installed". Trying to "DISABLE" it or "ENABLE" again does not do anything useful (it uninstalls the version I installed, but original is still missing).
So installing the store succeeds, it just doesn't seem to do anything. Example cmd I use for installation:
```
# adb install -r -d "com.android.vending_19.9.23-all_0_PR_309342545-81992300_minAPI16(armeabi,armeabi-v7a,mips,mips64,x86,x86_64)(nodpi).apk"
Performing Push Install
com.android.vending_19.9.23-all_0_PR_309342545-81992300_minAPI16(armeabi,armeabi-v7a,mips,mips64,x86,x86_64)(nodpi).apk: 1 file pushed, 0 skipped. 2.7 MB/s (21821561 bytes in 7.817s)
pkg: /data/local/tmp/com.android.vending_19.9.23-all_0_PR_309342545-81992300_minAPI16(armeabi,armeabi-v7a,mips,mips64,x86,x86_64)(nodpi).apk
Success
```
I tied extracting all the factory APKs from N910 stock images, but I can't easily figure out which APK stores the shop (yeah, I might try extracting them all, it's one line script after all).
Any idea what's going on, or what I should check?
Ooh..
```
adb install -r --user 0 "com.android.vending_19.9.23-all_0_PR_309342545-81992300_minAPI16(armeabi,armeabi-v7a,mips,mips64,x86,x86_64)(nodpi).apk"
```
That worked. It took me far too long to figure out.
So I uninstalled the app from "--user 0" - so from system apps, but tried to re-install it for local user instead. Turns out the Play services won't work if installed this way.
Issue solved.
I started to have exactly the same f***ing issue yesterday! I have wiped all data tried reinstalling ROM and still same errror... Why did this happen?
Does your fix corrects it forever?
I will need to try your solution. Thinking of moving to another custom ROM from almost original one.
Sadly I am getting INSTALL_FAILED_VERSION_DOWNGRADE.
What ROM do you have? Does this work only with stock ROM?
Condensing the story down for people who just want to solve constant "Application Google Play Services has stopped":
If you have this error, try downloading and installing "com.google.android.gms" APK in version "18.7.19".
You don't need to uninstall anything, you can just replace the existing package with:
```
adb install -r -d --user 0 "com.google.android.gms_18.7.19_(040300-262610125)-18719015_minAPI23(armeabi-v7a)(nodpi).apk"
```
options:
* -r will allow re-installing the package on existing installation
* -d will allow to downgrade the package if current version is newer
* --user 0 will install the package as system package, as the original package is installed this way (on Note4 stock images)
You need to find and download the proper APK file first, ofc.
I also have this problem with Google Play services constantly crashing and making phone almost unusable.
I tried clearing app cache, safe mode. Did not help. Only uninstalling updates for Google Play Services stopped constant crashes, but left about half of my apps unusable state because they relay to recent version of GMS.
I will try manually install recent working google play services .apk and see if it helps.
But how to stop automatic update of Google Play Services to the crashing one again? Automatic updates disabled everywhere, including Auto Update Google apps.
dib3ns said:
I also have this problem with Google Play services constantly crashing and making phone almost unusable.
I tried clearing app cache, safe mode. Did not help. Only uninstalling updates for Google Play Services stopped constant crashes, but left about half of my apps unusable state because they relay to recent version of GMS.
I will try manually install recent working google play services .apk and see if it helps.
But how to stop automatic update of Google Play Services to the crashing one again? Automatic updates disabled everywhere, including Auto Update Google apps.
Click to expand...
Click to collapse
Seems that clearing internal storage helped, so I think update + someold settings/data files causes this issue.
Could You please specify? By clearing internal storage You mean wipe all data?
Because Nothing helps, uninstalling Play Services updates, clearing app cache and even clearing the data. Also I cannot manually install google pay services .apk file, after installing it gives me installation failed. Play store installs Play Services, but they start crashing right after that.
Galaxy Note4 910F with stock 6.0.1 Android and Magisk rooted.
The issue returned for me, and I was able to make it go away again by clearing cache & data only for few specific apps. Details here:
[Solved] Error: "Unfortunately, Google Play Services has stopped" On different Note 4 Variants!!
Getting an error on multiple Note 4 variants N910V running Modest Rom & N916K (converted to N910C) running eRobot all within the last couple of days "Unfortunately, Google Play Services has stopped" , seems like a global issue anyone knows why &...
forum.xda-developers.com
I then allowed Google Store to update everything, and the issue didn't come back. So looks like the solution from the above thread really fixed it.
Solved for me. I updated Google Play services from Play Store and appears that Google fixed the botched update by releasing new version. Hope they never botch it again and not trash my phone, but more permanent fix needed, like completely preventing unnecessary auto updates to critical Android parts.

Categories

Resources