Database Users

How to prevent updates?

Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?

Delete OTACERTS.zip in system/etc/security. You must enable r/w and have root.
When I did It, it downloaded the update in front of me but didn't update. Then I deleted the update. Now i'm still on 6.2.1 and Loving It.

Molinari said:
Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?
Click to expand...
Click to collapse
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.

mark_a_l said:
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.
Click to expand...
Click to collapse
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.

iroctheworld said:
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.
Click to expand...
Click to collapse
What were you blocking? I've only got about 6 things on my white list (not blocked). Half are market related. In any case even if it doesn't work for OTA updates, I find some apps to be a bit too 'chatty' (looking at the logs). So it does work at blocking 'unnecessary' wifi traffic.

Thanks for the rename tip!

I am still avoiding the 6.2.2 update (only time can tell, last time mine was updated about 1 week after the first posting about forced updates ...)
I am running the rooted version of 6.2.1. I flashed this after losing root from the 6.2.1 forced update.
This time I only did two "mods" for protection -
(1) un-register from Amazon (actually I never register during ROM installation)
(2) use Droidwall
I dunno which one will make me survive the forced update, but I suspect it may / will be #(1).
I only allow a few things to go through Droidwall, most of them are 3rd party apps' names. The only two additional processes necessary for normal functions are:
(1) downloads, media storage, DRM protected content storage, download manager (needed for Market downloads)
(2) search (for Google search)
The one I always worry about in Droidwall is obviously #(1). I certainly do not let things like Amazon device client platform (ADCP) to go through!
This is just my Droidwall setup. People using other apps may need to allow other Android processes through therefore I cannot guarantee Amazon update won't sneak through that way.
I only know about the otacerts.zip when I revisited the forum yesterday afte reading elsewhere about the new OTA update. This time I won't modify this file on purpose.
(fingers crossed for me, I am not out of the woods yet)
P.S. Feb 2nd and I am still clean, looks like I dodged it!

Install Google apps without root and/or not affected by updates

Quite a while back, I lost root and I lost my Google apps functionality after a new update was pushed, and so I followed this thread to get my Google services working again: http://forum.xda-developers.com/showthread.php?t=1401486&highlight=google+services&page=1 <-- that thread contained links to a download of a file that installed like an app that "fixed" Google services frameworks and apps that were broken after an update was pushed, but that download is no longer available.
I had since rooted again using KFU, and when the last update to 6.3 was pushed, I was pleasantly surprised that the update, while breaking root again, did NOT screw up my Google apps -- gmail, maps and gTalk all still worked fine! I don't know how, but when I look in my system/app folder, the one that gets cleared/overwritten when updated, there are no Google services framework or app apks in there at all, yet my Google apps all work fine (not sure where the framework and apps are installed now). I have since rooted once again using KFU. I'm a bit techy, so I don't mind messing around a bit with my device, BUT....
I am getting a kindle fire for my mother -- I'm going to set it up with GO launcher, a bunch of sideloaded apps, and I would like to also install gmail, maps and gTalk without requiring root to be maintained, basically because I am then going to ship the device to her and will not want to continue to root and restore the google apps' functionality after every next update is pushed, because I would have to get her to do this while I walk her through the process over the phone, and this is not something that would make anybody happy.
So, I am hoping we can revive the discussion about how to install the Google services framework and apps without requiring root or at least in hopes that future updates will not break them. I am not opposed to rooting the device while I set it up, because I will want to install a permanent animated wallpaper, but I will unroot it so that Amazon Video will work before I send it off.
I have done quite a bit of searching through old threads, and there is not much talk about installing Google services and apps without root and so that updates don't screw with them. But I know it can be done, because it is working with mine.
I think this would be helpful to a LOT of people who are not yet ready to root and/or flash a new ROM.

If its the stock Kindle Fire interface you want, just root it and flash the MoDaCo rom. It comes prepackaged with gapps and gsf and (I think) you don't have to keep re-rooting .
http://forum.xda-developers.com/showthread.php?p=21282484

Thanks, but no ROMs. Gotta be stock kf with launcher and google apps.
All, I have a few assumptions and questions to bounce off you knowledgeable folks, since this is a forum of ideas:
As I recall, Google Services Framework and various Google apps are installed as "system apps" by using adb to push them to the system/apps folder. At least, I think this was how I did it back in December when I first got my Kindle Fire (maybe there are other ways, I dunno). And as system apps they install on bootup if not already installed. But the downside to these being installed this way is that when Amazon pushes an update, the update wipes the contents of the system/apps folder and replaces all apps there, so that our Google Services Framework and other Google apps are lost when Amazon updates.
Am I correct so far?
I have at some point installed Titanium Backup and possibly converted my Google Services Framework and other Google apps to "user apps", because when I look in the list of installed apps in Titanium Backup, I see that my Google Services Framework and other Google apps are listed in white and not red which means that they are "user apps" and not "system apps" (forgive my memory here, middle age is set in, so I don't remember what I have done with Titanium Backup -- should have kept a log).
So my questions: Could my Google Services Framework and other Google apps be now immune to Amazon updates screwing with them simply because they are user apps and not system apps (possibly converted with Titanium Backup)? Is this the solution to having Google Services Framework and other Google apps immune to Amazon updates? Am I answering my own questions (lol) or am I possibly missing something here?
Also, my Google Market app updated itself to Play Store at some point around the time that Amazon pushed update 6.3 and in Titanium Backup it is listed in green instead of red or white, so that there is no option to convert to system or user app.... not sure what that is all about.
If anybody is actually taking the time to follow me here, I appreciate it. I am just trying to figure out a way to take a brand new kindle fire, temp root it, set it up with all sorts of neat stuff like GO launcher, live wallpaper and Google apps galore, then unroot so that Amazon video works, and give it away as a super cool Android Tab for only $200 that is immune to Amazon Updates breaking the Google apps. This is my goal, and I hope it is useful to others as well.

bump?

gruuvin said:
So my questions: Could my Google Services Framework and other Google apps be now immune to Amazon updates screwing with them simply because they are user apps and not system apps (possibly converted with Titanium Backup)? Is this the solution to having Google Services Framework and other Google apps immune to Amazon updates? Am I answering my own questions (lol) or am I possibly missing something here?
Click to expand...
Click to collapse
I think you are basically correct. Other than GoogleCalendarSyncAdapter.apk, none of my google apps have stopped working after an Amazon update, and while I did nothing special to cause this, the speculation around here has been that updates to the apps caused them to get installed properly as user apps so they would keep working. What you may have done with titanium backup may have had the same effect, or it may have been coincidence (I will definitely have to check Titanium backup and see if I can do anything with GoogleCalendarSyncAdapter, because if I can get that to survive updates, I won't have much need to root anymore).

I will try this today as I am doing a similar thing and anything that can prevent the google app store from stopping will be much appreciated.

I've had my Fire since January. Never rooted but did install Google services framework the first week I got it. Pretty sure this is the thread I followed to do it: http://forum.xda-developers.com/showthread.php?t=1401486 I've sideloaded Gmail, Books, Reader, Google+, Google Music and Youtube. All have continued to work fine after 2 updates from Amazon. So far the only Google apps that haven't worked for me were Currents and Play Store. As long as those 2 apps aren't dealbreakers this would accomplish most of your goals. You can change the stock wallpaper and get it to stick by using he app Rotating Wallpaper (not sure if it supports live wallpapers). By doing these things and using GoLauncher my Fire does everything I want it to without rooting. One other thought... you might want to consider putting Dropbox on it with a folder you can put apps (and updates) in to share with your Mom. Good luck.

I just checked and Google Talk doesn't work doing it this way. Also, the app Rotating Wallpaper doesn't support live wallpapers.

soupmagnet said:
If its the stock Kindle Fire interface you want, just root it and flash the MoDaCo rom. It comes prepackaged with gapps and gsf and (I think) you don't have to keep re-rooting .
http://forum.xda-developers.com/showthread.php?p=21282484
Click to expand...
Click to collapse
You don't have to keep rooting? Are we sure about this? I have been reading about the MoDaCo ROMs and seeing the question asked, "will it still get the pushed Amazon updates?", and so far the answers have been yes. So it will get the amazon updates, which always break root and play store. Sure we could reflash the ROM but then it will get the update again, and on and on.
Are MoDaCo ROMs immune to Amazon updates? Are MoDaCo ROMs immune to Amazon updates breaking root and PlayStore?
I am really hoping that someone can confirm the above response, because if not, it will be a lesson learned about not believing the misinformation that some folks hastily post as a response to a question without actually addressing the question. I know he qualified it with "(I think)"... I should have paid more attention and confirmed that thought.
The reason I ask is because 6.3.1 was pushed to both mine and my mother's KFs a few nights ago just before I was ready to send it off to her for Mother's Day, and mine was bricked as a result, until I spent a couple of hours poking at it with KFU and adb to get it to properly boot and flash the updated ROM Amazon pushed. After that headache, I didn't want that to happen to my mother's with the next update in a month if I could not be around to fix it. So I decided to take the next step and load a ROM, MoDaCo GR8, on both mine first and then my mother's, and I already sent hers off yesterday, in haste. I am reading today that what was implied above may not be true -- that MoDaCo ROMs do get the Amazon updates and when Amazon pushes the next update, her KF could lose root and Play Store at best and be bricked at worst.

Without root, how can you mount system as rw?
Gửi từ Kindle Lửa của tôi qua Tapatalk 2

gruuvin said:
You don't have to keep rooting? Are we sure about this? I have been reading about the MoDaCo ROMs and seeing the question asked, "will it still get the pushed Amazon updates?", and so far the answers have been yes. So it will get the amazon updates, which always break root and play store. Sure we could reflash the ROM but then it will get the update again, and on and on.
Are MoDaCo ROMs immune to Amazon updates? Are MoDaCo ROMs immune to Amazon updates breaking root and PlayStore?
I am really hoping that someone can confirm the above response, because if not, it will be a lesson learned about not believing the misinformation that some folks hastily post as a response to a question without actually addressing the question. I know he qualified it with "(I think)"... I should have paid more attention and confirmed that thought.
The reason I ask is because 6.3.1 was pushed to both mine and my mother's KFs a few nights ago just before I was ready to send it off to her for Mother's Day, and mine was bricked as a result, until I spent a couple of hours poking at it with KFU and adb to get it to properly boot and flash the updated ROM Amazon pushed. After that headache, I didn't want that to happen to my mother's with the next update in a month if I could not be around to fix it. So I decided to take the next step and load a ROM, MoDaCo GR8, on both mine first and then my mother's, and I already sent hers off yesterday, in haste. I am reading today that what was implied above may not be true -- that MoDaCo ROMs do get the Amazon updates and when Amazon pushes the next update, her KF could lose root and Play Store at best and be bricked at worst.
Click to expand...
Click to collapse
I can tell you that I flashed MoDaCo GR8 before the recent push of 6.3.1 and my KF was not affected at all by the update. I wouldn't have known that there had been an update if I hadn't read about it here. I have also read 3 or 4 post by other GR8 users indicating that they hadn't been affected either. I read the entire MoDaCo thread and I am pretty sure that the developer made a comment in it somewhere that he was incorporating something that he hoped would prevent the auto updates from messing things up. Based upon my experience it looks like he was successful.
Now for the disclaimer, just because MoDaCo wasn't affected this time doesn't guarantee that it won't be affected by future updates.
Sent from my Kindle Fire using xda premium

linktohack said:
Without root, how can you mount system as rw?
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
Click to expand...
Click to collapse
Code:
adb root
adb remount

Thanks JimCo!! This is what I'm really hoping to hear! I'm keeping my fingers crossed. I really do like the whole idea that is the MoDaCo ROM.

Fire HD 8 [2016][6th Gen] 5.3.2.1 - What's Currently Possible?

Hi All,
I was very happy to see that root has been achieved for our device but unfortunately not for v5.3.2.1. The root thread says that any attempt to downgrade 5.3.2.1 by sideload will result in a hard brick.
1. Will a factory restore leave me at 5.3.2.1 or will I be downgraded to something that can be worked with?
2. Is there any way to prevent updates on the device itself? I don't want to hear that a root for 5.3.2.1 has become available only to find that I've been silently and automatically upgraded. I'm not really interested in trying to block addresses on the router, unless that's truly the only option.
3. When sideloading apps, what is the correct location for obb files? The two Android/obb folders have empty folders with the names of some working apps I've installed, but no actual obb files in the app subolders. (e.g. obb/appname/appname.obb -there's no appname.obb file. Does the Kindle put the obbs somewhere else)
4. Other than getting the playstore on the device, is there anything else we can do with 5.3.2.1?
My main reason for root is for AdAway. The others don't seem to block ads in apps...
Thanks for the help.

xdax32 said:
Hi All,
I was very happy to see that root has been achieved for our device but unfortunately not for v5.3.2.1. The root thread says that any attempt to downgrade 5.3.2.1 by sideload will result in a hard brick.
1. Will a factory restore leave me at 5.3.2.1 or will I be downgraded to something that can be worked with?
2. Is there any way to prevent updates on the device itself? I don't want to hear that a root for 5.3.2.1 has become available only to find that I've been silently and automatically upgraded. I'm not really interested in trying to block addresses on the router, unless that's truly the only option.
3. When sideloading apps, what is the correct location for obb files? The two Android/obb folders have empty folders with the names of some working apps I've installed, but no actual obb files in the app subolders. (e.g. obb/appname/appname.obb -there's no appname.obb file. Does the Kindle put the obbs somewhere else)
4. Other than getting the playstore on the device, is there anything else we can do with 5.3.2.1?
My main reason for root is for AdAway. The others don't seem to block ads in apps...
Thanks for the help.
Click to expand...
Click to collapse
Unfortunately once on the latest, you're always on the latest. The only thing we can really do is install Google Apps and the Play Store. Also unfortunately, I cannot answer any of your other questions. I got my Kindle to put into my dashboard of my truck so not doing much with it other than play music.
Edit: Okay I take that back, I can answer the Update question. The only current way for us unrooted folks to not get updates automatically, is to factory reset, setup Kindle, NEVER OPEN THE UPDATE SETTING!!!! I thought that mine auto updated on it's own, but I found out that my wife was dicking around on it and went in the update section by accident. When she got done and put it to charge, it updated.

How to make Location services work?

I was not planning to root my Fire HD 10 (7the generation) OS 5.6.2.0 so I got the 4 google account files set up as per instructions. Worked perfect. Then I installed Nova Launcher and had to add Launcher Hijack to make it stick. All worked great except no widget support. Solved that with some ADB commands also found here on XDA.
Now I discovered same as others that my location services do not work but could not find a way to make it work without undoing all I did, rooting it and then doing it all again with root. Can I avoid rooting and redoing it with any fix on top of what I already done?

MutantWizard said:
I was not planning to root my Fire HD 10 (7the generation) OS 5.6.2.0 so I got the 4 google account files set up as per instructions. Worked perfect. Then I installed Nova Launcher and had to add Launcher Hijack to make it stick. All worked great except no widget support. Solved that with some ADB commands also found here on XDA.
Now I discovered same as others that my location services do not work but could not find a way to make it work without undoing all I did, rooting it and then doing it all again with root. Can I avoid rooting and redoing it with any fix on top of what I already done?
Click to expand...
Click to collapse
This has worked consistently through numerous resets. This hasn't failed me yet. The key is to make sure location services are turned on before installing any Google apps or deleting bloatware. See here: https://forum.xda-developers.com/hd8-hd10/help/fix-how-to-google-location-services-t3813111

DragonFire1024 said:
This has worked consistently through numerous resets. This hasn't failed me yet. The key is to make sure location services are turned on before installing any Google apps or deleting bloatware. See here: https://forum.xda-developers.com/hd8-hd10/help/fix-how-to-google-location-services-t3813111
Click to expand...
Click to collapse
Thanks for the response!
I saw this before but was not sure I wanted to go down that road. Well I decided and here I go. I intend to try the following root process. Please let me know if any other preferred method is likely to be more reliable.
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-offline-rooting-t3734860

Its done and working!

The Play Store just un-rooted my HD8/deleted SuperSU, w/out my permission - WTF?? ?

I'm angry/confused - has anyone else had this happen to their device?
Last night, I sat down and rooted one of my 2017 HD8 tablets, following the damn-amazing Experimental Software Root method as recently uncovered and shared with us by @diplomatic. I then installed SuperSU (from the damn Play store!) to take the root from temporary to permanent.
I spent the last 24 hours FINALLY being able to use my Fire tablet as a semi-solid/functional personal computing device, finally able to really setup the device to perform as I need it to, and I've been very happy with how everything turned out.
Well, I just came back to my desk to find a message from "Play Protect," (a feature/service I ALWAYS turn off in Play Store settings, on all of my devices):
App Removed by Play Protect: SuperSU
This app can allow unauthorized access to your data or device.
(see images attached).
I checked and no longer have root status. Also, now I can't install any .apk files whatsoever. WTF??!
I downloaded SuperSU... FROM THE PLAY STORE...! The app is listed and available for installation from/by the Play Store (see attached photo).
So, I guess now I will just re-root and hope in the future Google chills the F out/gets their creepy little hands out of my device/data. Maybe I should freeze the Play Store/Play Services? I just wanted to see if anyone else had ever had this happen to them/if there is a recommended solution. SO annoying!!! ??‼?‼??
(pardon my grumpiness/I feel a little bit better now, post vent ?)

Ok - I'll stop whining now... ?
I was able to recover root by simply reinstalling "SuperSU" from the Play Store. Hopefully it was just a fluke and everything will stay where it should be.

richaardvark said:
Ok - I'll stop whining now... [emoji51]
I was able to recover root by simply reinstalling "SuperSU" from the Play Store. Hopefully it was just a fluke and everything will stay where it should be.
Click to expand...
Click to collapse
I had exact same thing happen but once reinstalled from play store it has been fine.
Sent from my SM-G960U1 using Tapatalk

richaardvark said:
I'm angry/confused - has anyone else had this happen to their device?
Last night, I sat down and rooted one of my 2017 HD8 tablets, following the damn-amazing Experimental Software Root method as recently uncovered and shared with us by @diplomatic. I then installed SuperSU (from the damn Play store!) to take the root from temporary to permanent.
I spent the last 24 hours FINALLY being able to use my Fire tablet as a semi-solid/functional personal computing device, finally able to really setup the device to perform as I need it to, and I've been very happy with how everything turned out.
Well, I just came back to my desk to find a message from "Play Protect," (a feature/service I ALWAYS turn off in Play Store settings, on all of my devices):
App Removed by Play Protect: SuperSU
This app can allow unauthorized access to your data or device.
(see images attached).
I checked and no longer have root status. Also, now I can't install any .apk files whatsoever. WTF??!
I downloaded SuperSU... FROM THE PLAY STORE...! The app is listed and available for installation from/by the Play Store (see attached photo).
So, I guess now I will just re-root and hope in the future Google chills the F out/gets their creepy little hands out of my device/data. Maybe I should freeze the Play Store/Play Services? I just wanted to see if anyone else had ever had this happen to them/if there is a recommended solution. SO annoying!!!
(pardon my grumpiness/I feel a little bit better now, post vent ?)
Click to expand...
Click to collapse
I had a similar experience today when updating some apps I got from the Google Play Store. During the updates, it deleted my SuperSU with no warning or asking permission. Luckily, it didn't affect my root as far as I can tell. I too got SuperSU from the Play Store. It is DEFINITELY annoying !

Two things when installing play store. Always good to 1) immediately turn off auto updates the second you sign in. 2) turn off play protect.
As soon as play services updates, all apps will start to update if they are allowed. So make sure to look at 'my apps', and make sure none are stuck in que. If so, tap 'stop all'.

I am having the exact same issue. Nothing seems to be working no matter what I disable. it keeps removing supersu
Has anyone tried anything that works?

neodenjin said:
I am having the exact same issue. Nothing seems to be working no matter what I disable. it keeps removing supersu
Has anyone tried anything that works?
Click to expand...
Click to collapse
Try SuperSU v2.79. Grab it from this post here. Playstore has problems with V2.82

unixtan said:
Try SuperSU v2.79. Grab it from this post here. Playstore has problems with V2.82
Click to expand...
Click to collapse
Just don't update from the play store unless you downloaded it there and if you do update, do so manually by downloading standalone apk and installing it through documents or a root explorer. I'm trying to work on a fix for this version in some form. We can't flash it unless you use the modified version on the stock rom thread because we aren't quite 64 bit yet. Flashing the standard zip will bootloop. So I've been experimenting with a totally manual install, including rooting the boot.img so when the apk is installed it doesn't perform the auto install embedded into it. So far, though I don't really know yet, it appears to be a success. One of the issues, I think, was the installation of the 64 bit library file. Either it install it, but in the regular lib folder, or doesn't install it at all or does install but doesn't set proper permissions (guesswork). So I added the necessary files by unpacking and repacking the boot.img. This is not a final version.I'm, but If anyone is interested in trying it out I can upload the boot.img.