Fire HD 8 [2016][6th Gen] 5.3.2.1 - What's Currently Possible? - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

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.

Related

[Q] How Do You Prevent \Nook From Updating?

How do you stop the B&N firmware updates?
I’m running 1.0.0 and have no desire to have my Nook updated and lose all my hard work.
I’ve had it one day and I have rooted, installed Market, downloaded tons of apps that work on my DX and don’t have any issues yet.
Even the Demo of NFS Shift works on this thing!
Just say no to an update.
I searched xda a few days ago and found this way to prevent updates (I changed the words a bit in my personal notes) - I can take no credit for this method...
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Hopefully this will do the trick.
I'm rooted on 1.0.0 as well and have been for a few days now. I haven't been updated OTA to 1.0.1 at all. I read somewhere that once your'e rooted, OTA doesn't work. Is that true? Or should I take this precautionary step as well?
Do a titanium backup and don't worry about it either way...
Sent from my NookColor using XDA app
Don't do the above if you use the B&N Store. It'll cause your device to reset.
deleted...wrong post
Mikroft said:
Don't do the above if you use the B&N Store. It'll cause your device to reset.
Click to expand...
Click to collapse
Thanks for the heads up. I've already got a Titanium backup on my apps so I should be ok if mine resets. I'll leave mine as is for the time being.
tech_head said:
How do you stop the B&N firmware updates?
I’m running 1.0.0 and have no desire to have my Nook updated and lose all my hard work.
I’ve had it one day and I have rooted, installed Market, downloaded tons of apps that work on my DX and don’t have any issues yet.
Even the Demo of NFS Shift works on this thing!
Just say no to an update.
Click to expand...
Click to collapse
So why didn't you update to 1.0.1 as suggested in the nookdevs wiki?
Mikroft said:
Don't do the above if you use the B&N Store. It'll cause your device to reset.
Click to expand...
Click to collapse
1- Does "do the above" refer to changing the name of the OTA file or does it refer to making a Titanium backup? (I assume the first?)
2- Does "if you use the B&N Store" refer to shopping for a book on wifi or going into a physical B&N store?
So... our choice is to stop an update and loose the store or get the update and possibly lose our root?
barbo said:
1- Does "do the above" refer to changing the name of the OTA file or does it refer to making a Titanium backup? (I assume the first?)
2- Does "if you use the B&N Store" refer to shopping for a book on wifi or going into a physical B&N store?
So... our choice is to stop an update and loose the store or get the update and possibly lose our root?
Click to expand...
Click to collapse
As in don't do the OTA file modification above if you use the B&N online store on the Nook. I don't think it's been proven either that the file mod absolutely prevents an update as sometimes it differs per device. I have the file modded but I don't use the B&N online store.
Developer To Do
Good topic. It would be great if one of this forums many great developers could solve this conundrum. Many of us who have rooted our NookColors would like to retain the rooted status but be able to use the B&N store without fear of unrooting the NC.
Mikroft said:
As in don't do the OTA file modification above if you use the B&N online store on the Nook. I don't think it's been proven either that the file mod absolutely prevents an update as sometimes it differs per device. I have the file modded but I don't use the B&N online store.
Click to expand...
Click to collapse
I had the file modded and I was able to use the store to buy books just fine.
I changed the file name on 12/17 to stop updates . I "Shop" several times a week. No issues at all.
SCIONTX said:
I changed the file name on 12/17 to stop updates . I "Shop" several times a week. No issues at all.
Click to expand...
Click to collapse
SCIONTX and KitF, do you have titanium backup installed? In another thread, someone is thinking the problem might be due to installing and/or using titanium backup.
Explanation of how to avoid forced B&N Reset when using Titanium backup / restore
barbo said:
SCIONTX and KitF, do you have titanium backup installed? In another thread, someone is thinking the problem might be due to installing and/or using titanium backup.
Click to expand...
Click to collapse
To the best of my knowledge, as is also discussed in the other thread on the B&N forced reset + Titanium ...
A B&N forced reset will occur if you restore an old login registration certificate for your device. This would occur if you make a full Titanium backup (including various system settings), de-register your Nook Color, (wipe, etc.), re-register (this creates a new certificate in on the Nook and in the B&N Shop itself associated with your B&N login), and then restore "too much" using Titanium.
The solution (so far) is to be very selective as to what you restore with Titanium ... i.e., I avoided restoring "anything" remotely system settings for B&N , whisper, shop, sync, etc.. There likely is only one "settings" to be avoided, but I don't know which one.
Side note: I also read that having a mismatch between your Google login and your B&N Login can confuse the B&N server and force a reset. This one does not make as much sense to me.
OK folks,please forgive me if the following questions have been answered already. I just need some clarification.
I recently side loaded apps to my NT,including Launcher Pro and Button savior so I can recal the NT launcher if I need to. I boot into Launcher Pro and I like the interface and ability to see all of my sideloaded apps in a grid view instead of having to do a search via the NT's launcher.So am I right in assuming that,technically, I have not rooted my NT? If this is the case,how do I avoid the OTA updates? As of last night,Dec 29th,I was still able to install apps and have them launch and run just fine. I really don't want the firmware update! Can someone just clarify the steps I need to take as I don't know if the work around discussed here applies to me.
meshica7 said:
[...] I recently side loaded apps to my NT,including Launcher Pro and Button savior so I can recal the NT launcher if I need to.
Click to expand...
Click to collapse
Nook TABLET (NT) or Nook COLOR (NC)? They are different devices.
If you're able to install apps from the Market, it does sounds as if you've rooted properly. I blocked updates on my NC and my wife's NT using the SQLite database edit, and have not had any problems with recent updates.
I'm very interested in this topic as I'm preparing to noot my Nook Color. But I feel that I've missed something. How do you block updates "using the SQLite database edit"?

[Q] KF Do over - back to 6.2

I fell into the 6.2.1 trap before I got Google Android Market installed. As a result of a partial market installation, I get periodic errors about the android market that pop up and need to be forced closed. I plan to do a factory reset and return the device to the store then buy a new one with the original OS. I need to know what to do so I can get it working with Android Market OTA.
Since the tablet has only 6+ GB to play with, I don't want to load it with too many hacking type tools or other OS. I am interested in seeing how Titanium Backup works but I don't know if I want to keep the KF permananently rooted. My main goal is to have Android Market available and working wirelessly. I am also trying do decide whether to block the the OTA update from Amazon permanently or just until I get my basic Google apps installed. So my plan is:
Get a new Kindle Fire with old OS
Leave WiFi off
Root with Super One Click
Install Google Android Market
Disable rerouting to Amazon Market
Am I right assuming that once installed, Google Android Market will continue to function once Amazon updates me to the latest version?
I also want to make sure that I have Google Mail and Google Maps and I don't know if 6.2.1 unrooted prevents installing those. I like the ability of the 6.2.1 to get rid of junk on the carousel and the scrolling speed seems a little better now. Of course videos are playable with unrooted KF.
Am I missing any steps or are there other recommendations?
You should be able to install Google maps and Gmail onto a regular 6.2.1 KF without any problems.
I don't think there's a known method to block the update while keeping full online functionality.
The best thing at the moment is to install a premodded 6.2.1 update with root access so you can install the Market Place etc.
In anycase if you return the unit for a new one there could (and probably will) be another update in a few weeks. So far there's been an update every couple of weeks since it came out. Each time you lose root and are back to square one.
I'm waiting for someone more clever than me to find a workaround to get root access back on a 6.2.1...
PS - 6GB is a lot of room for installing apps! I wouldn't worry about running out of room unless you're filling up your KF with downloaded media.
oh and PPS - Amazon updates can easily stop the market place from working. The 6.2.1 update has stopped mine from working (because I had it installed in /system/app which is one of the folders replaced in the last update.)
Got new 6.0 KF - Bootstrapping Catch 22
So I returned the 6.2.1 version and got a new one with 6.0 still installed. Now I find that I have no way of loading any apps with the stock unit. The directories that show up on the device through the USB connection are very limited. I copied the root explorer app to the documents directory but naturally it does not show up.
Without having a file explorer app, I don't know how to proceed. If I turn on and register the Kindle, I am liable to get updated immediately. If I can just get to the Amazon store and get a file explorer app and then quickly turn off wireless I may luck out. Are there any other ways to get an app installed without having an app like root explorer or similar without having to first go to Amazon market?
6.2.1? I'm still on 6.2. What's the deal? Why did i not get the update?
Update - I was able to quickly register and bring in the root explorer app. I then turned off WiFi and found I was still at 6.0. Now to try to root it...

12/25, what's the current root method?

Hi guys, I just got my Kindle Fire for xmas today. I want to root, but I've been reading the forum and see that a recent OTA update came out and there's been problems. I'm not super computer savy and I really don't want to mess it up. Do I have to wait for a new method to root? If someone wants to take a newb under their wing and tell me what roms etc I should get it would be much appreciated! Just a little overwhelmed with all the posts, not sure where to get consolidated current info.
I haven't even turned it on yet, I'm not sure if I should wait to turn it on, so that if it doesn't have the OTA update it doesn't send through as soon as I turn it on... whatever advice anyone can give would be much appreciated!
For Windows, Use this http://forum.xda-developers.com/showthread.php?t=1399889
Tired that version today works wel..
I haven't turned my Kindle on yet, can I avoid all the complications by somehow keeping it from getting the OTA update when it turns on? (I'm assuming it's not running 6.2.1 yet because that just came out?) I'm afraid to turn it on and I really want to play with it so if someone can let me know that would be great!
And if anyone wants to talk me through it, my screenname is Insidious Lily on aim, I need moral support/help, lol.
Just keep WiFi off until you are done... no issues.
Okay.. I'm a little overwhelmed by all the stuff in that post but I'll do my best. I'm in that IRC chat with another newb if you want to come help us, haha.
And high five, I have a HTC incredible too.
How about current method for Mac users?
ty!
So here's what I did...
(I have a Mac running snow leopard).
I downloaded the KindleFireRootMacLinux folder referenced in the old Mac root thread. This gets adb running on the mac. Use whatever system you need to get adb running on your PC. The command adb on the PC is replaced by ./adb-mac on the Mac.
Then I used the burrito root method and pushed super user to the kindle fire. using the adb commands from terminal.
Finally, I downloaded the google apps folder, installed Googleservicesframework *FIRST* and rebooted.
Then I installled the remainder of the apps EXCEPT market.
Then I used the ES Folder program with root explorer etc enabled to copy the market.apk file to system/app and changed permissions and ran it.
Everything worked fine.
THEN I installed DroidWall to take away the internet communication capabilities of all the Amazon apps (and browser) to try and keep another stealth push from Amazon from breaking root.
Someone else will have to link to the files because I haven't posted enough to include links.
Current root is BurritoRoot http://forum.xda-developers.com/showthread.php?t=1410223
if your particularly lazy Vashypooh's utility has been updated to use it here http://forum.xda-developers.com/showthread.php?t=1399889
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
leebo said:
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
Click to expand...
Click to collapse
Yep, but we did discover it doesnt work with 6.0 this morning. Seems what I used wasn't fully introduced until after 6.0

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!

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.

Categories

Resources