Database Users

Complete video tutorial from open box to root, XBMC, Google Play Store, etc.

Hey there! I put together a complete video walkthrough for converting your FireTV to an XBMC box.
This includes:
Root
Preventing Amazon updates
Making XBMC the launcher
Installing apps to XBMC homepage
Demo of Mupen64+(N64 emulator) and Reflector (Airplay)
Remember, if you are buying a new FireTV, make sure to follow the instructions here to make sure it doesn't update to an unrootable version. In short, either block access at the router level, or disconnect wifi / ethernet right after you start the device and connect to the network, before the download of the new version can finish.
Enjoy! Let me know if you'd like me to do video walkthroughs of anything else, like using stickmount, connecting to Windows computers over the network, etc.

hotterpop said:
Hey there! I put together a complete video walkthrough for converting your FireTV to an XBMC box. This includes:
Root
Preventing Amazon updates
Making XBMC the launcher
Installing apps to XBMC homepage
Demo of Mupen64+(N64 emulator) and Reflector (Airplay)
Remember, if you are buying a new FireTV, make sure to follow the instructions here to make sure it doesn't update to an unrootable version. In short, either block access at the router level, or disconnect wifi / ethernet right after you start the device and connect to the network, before the download of the new version can finish.
Enjoy! Let me know if you'd like me to do video walkthroughs of anything else, like using stickmount, connecting to Windows computers over the network, etc.
Click to expand...
Click to collapse
Sweet, nice!

Great walk through wish I could use the whole lot.
Mainly using xbmc and its a great improvement on my Pi but as I am in UK no root so a "here's what you can do with unrooted AFTV" vid would nice, having said that the llama trick for short cut works great and I don't think I need much more

Great Effort. You should do another tutorial using FireTVUtility. I would be easier, w/o any commands to type directly in adb shell.

Legolas2 said:
Great Effort. You should do another tutorial using FireTVUtility. I would be easier, w/o any commands to type directly in adb shell.
Click to expand...
Click to collapse
I'll look into it. It doesn't look like it really needs any help though- I haven't used this program in particular, but my experience with pc-side all in one solutions is that if they work, they work, and if they don't, there's not much the user can do to fix it. It also seems that the developer is pretty active, so any video I make may be out of date rather quickly. That being said, if other folks agree that there should be a tutorial for this, I'll put it together.
Thanks for passing this utility on, though. Tools like this were essential to me when I started messing with cm 10 on an old phone of mine last year, which extended its useful life until I got my (glorious) OnePlus in July. My experience there really hit me with the modding bug, and I have been messing with android since. The purpose of the video was to help introduce people to the idea that android is open and ready to tinker with, in addition to taking advantage of the FireTV's potential with Kodi. If you have any more requests though, I'd love to hear them, and I'll do my best to fulfill them as time permits

Launcher
Hey, Thx for the awesome Video. Just a question....How do you get it to automatically boot into XBMC? I want to use XBMC as my home screen/launcher like you have shown in your video. I really appreciate it! Thanks!

Correction: HDExposed section
Kdurahm said:
Hey, Thx for the awesome Video. Just a question....How do you get it to automatically boot into XBMC? I want to use XBMC as my home screen/launcher like you have shown in your video. I really appreciate it! Thanks!
Click to expand...
Click to collapse
Hey there,
Sorry about the confusion. Looks like in my hasty editing I accidentally cut out a step. I've added an annotation to the video that addresses this, so you should be set if you re-watch minutes 21-25 of the video. I accidentally forgot to include that you need to go into the Modules section of HDExposed and, using a mouse, check the two boxes there as well before you reboot.
Thanks for pointing that out!

This is a great tutorial! Thank you
I have a couple of other fire TVs to root that I'm going to pass off to my friends. If
I complete the root and disable the ota updates at my house, when they plug it in their home, the firetvs won't loose the root right? Should they still add the 2 sites to block
On their router?

Berrybare said:
This is a great tutorial! Thank you
I have a couple of other fire TVs to root that I'm going to pass off to my friends. If
I complete the root and disable the ota updates at my house, when they plug it in their home, the firetvs won't loose the root right? Should they still add the 2 sites to block
On their router?
Click to expand...
Click to collapse
Hey there!
Glad you like my walkthrough. If you use the router-level blocking method, it will need to be applied to any and every network the FireTV connects to. This is a great way to guarantee that the FireTV does not update, but should only be considered a temporary method until you can disable updating permanently on the device itself. If you go to around minute 14 of my video, you'll see how to disable the update function on the device itself. This is the only way to guarantee that the device won't update in the future, no matter what it connects to.
Because of the issue with devices connecting and automatically updating to an unrootable version, I'd recommend you do the network-level update blocker (like it sounds like you've already done) and then use the device-level root prevention I described in the video.
Please let me know if you have any questions

Berrybare said:
This is a great tutorial! Thank you
I have a couple of other fire TVs to root that I'm going to pass off to my friends. If
I complete the root and disable the ota updates at my house, when they plug it in their home, the firetvs won't loose the root right? Should they still add the 2 sites to block
On their router?
Click to expand...
Click to collapse
Ultimate protection is having CWM aka custom recovery install. On top of the disabled OTA Update. Both done very easily with the AFTV Utility app mentioned above... Everybody should keep their routers blocking the IP's. Specially if you are going to be working on non-rooted AFTV's. But you can run an CWM'd AFTV on an unblocking router if it can't be helped.
hotterpop said:
Hey there!
Glad you like my walkthrough. If you use the router-level blocking method, it will need to be applied to any and every network the FireTV connects to. This is a great way to guarantee that the FireTV does not update, but should only be considered a temporary method until you can disable updating permanently on the device itself. If you go to around minute 14 of my video, you'll see how to disable the update function on the device itself. This is the only way to guarantee that the device won't update in the future, no matter what it connects to.
Because of the issue with devices connecting and automatically updating to an unrootable version, I'd recommend you do the network-level update blocker (like it sounds like you've already done) and then use the device-level root prevention I described in the video.
Please let me know if you have any questions
Click to expand...
Click to collapse
Although I would wait for the next release of both apss (adbFire & AFTV Utility) since so much has change the last 24 hours (unlock bootloader + new CWM). I would love to see a video using the AFTV Utility app to take care of all including the new options. Including the Mount external USB storage script.... It would be massive but all encompassing. I think the only thing waiting for an update is RBox's [XPosed] Mod's... Specifically the menu items part...

Sounds great. Post here when the new software is ready and I will get recording!

hotterpop said:
Sounds great. Post here when the new software is ready and I will get recording!
Click to expand...
Click to collapse
Great.. Will let you know when it gets posted..

hotterpop said:
Hey there!
If you go to around minute 14 of my video, you'll see how to disable the update function on the device itself. This is the only way to guarantee that the device won't update in the future, no matter what it connects to.
Click to expand...
Click to collapse
Is there an adb command to verify the "pm disable com.amazon.dcp" status. I ran this command months ago and have had no unwanted updates ruin root on the Fire TV. Perhaps, it is not necessary but just looking to be sure.

mjbxx said:
Is there an adb command to verify the "pm disable com.amazon.dcp" status. I ran this command months ago and have had no unwanted updates ruin root on the Fire TV. Perhaps, it is not necessary but just looking to be sure.
Click to expand...
Click to collapse
I don't know, but if you don't have router level blocking and you haven't received any updates, you are safe. Usually the update occurs quite quickly.

hotterpop said:
I don't know, but if you don't have router level blocking and you haven't received any updates, you are safe. Usually the update occurs quite quickly.
Click to expand...
Click to collapse
Sorry for bumping, I just wondered if there was any advance on the new software/video?
I have an untouched UK AFTV and just waiting for this video with new software for the complete start to finish setup before i do something wrong!
Let me know if im better off just following your first video if this new software stuff is not going to be released for a while.
Thanks

My recommendation is always to code by hand. That's how I learned, and I feel like it's a great way to learn about how Android really works. That being said, it's not for everyone, and I understand any nervousness you may have.
I'll probably have the video using the tool by the end of the week.

hotterpop said:
My recommendation is always to code by hand. That's how I learned, and I feel like it's a great way to learn about how Android really works. That being said, it's not for everyone, and I understand any nervousness you may have.
I'll probably have the video using the tool by the end of the week.
Click to expand...
Click to collapse
Unfortunately im not very technically minded, and would end up messing up unless I followed a guide from someone who knows their stuff!!
I will keep it in the wrapper until you can bring out the new video, id feel a lot safer and not end up bricking it or non rootable forever!
If i can make one request, I really will just want to use the AFTV for XBMC and maybe some emulators... So if its possible to include how to have the quickest access to XBMC from boot, id really appreciate it. Not sure how easily that is done with a non rootable AFTV?

swiss_lis said:
Unfortunately im not very technically minded, and would end up messing up unless I followed a guide from someone who knows their stuff!!
I will keep it in the wrapper until you can bring out the new video, id feel a lot safer and not end up bricking it or non rootable forever!
If i can make one request, I really will just want to use the AFTV for XBMC and maybe some emulators... So if its possible to include how to have the quickest access to XBMC from boot, id really appreciate it. Not sure how easily that is done with a non rootable AFTV?
Click to expand...
Click to collapse
I understand your concern. However, I would definitely consider rooting the device. While you can use XBMC and play emulators on the FTV without root, it is pretty inconvenient. Rooting isn't hard, and shouldn't be something that scares you at all.
If you are willing, my video shows you exactly what to type every step of the way. There's lots of support if you get lost, and you can always ask me questions here- I don't mind looking up documentation for you if you need it. If you have access to your router, once you have blocked the update sites there, you will be safe to take as long as you need to.
I'll try to have the other videos done soon. I wish I had more time in my life right now for stuff like that, but you know we all have to make a living somehow
I'll be sure to post in here when the tutorials are done.

swiss_lis said:
Sorry for bumping, I just wondered if there was any advance on the new software/video?
I have an untouched UK AFTV and just waiting for this video with new software for the complete start to finish setup before i do something wrong!
Let me know if im better off just following your first video if this new software stuff is not going to be released for a while.
Thanks
Click to expand...
Click to collapse
swiss_lis said:
Unfortunately im not very technically minded, and would end up messing up unless I followed a guide from someone who knows their stuff!!
I will keep it in the wrapper until you can bring out the new video, id feel a lot safer and not end up bricking it or non rootable forever!
If i can make one request, I really will just want to use the AFTV for XBMC and maybe some emulators... So if its possible to include how to have the quickest access to XBMC from boot, id really appreciate it. Not sure how easily that is done with a non rootable AFTV?
Click to expand...
Click to collapse
Those that bought their FTV's in the UK or GER & did not import US FTV's. The best you can hope for right now is block the two IP's so it doesn't keep auto updating. In case there is ever a new rooting option. UK & GER FTV's can not be rooted. You should setup your FTV with XBMC & anything else you would like within the unrooted options.
Once you have properly blocked update IP's & boot up & check your FW version which 99.99% chance it will be 51.1.4.0_user_514006420 (Unrootable) . You should feel safe to play with your FTV...
What router do you have ?? This link just shows you pictures of different IP blocking router interfaces like Tomato, DD-WRT, Asus, NetGear, Untangle, OpenDNS..
http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/
This one tells you what to block now...
http://www.aftvnews.com/how-to-setup-a-new-fire-tv-without-blocking-root/
Method 1: Domain blocking with Router – Recommended Method
1. Before powering on the Fire TV, go into your router’s settings and block access to the following two domains:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
If you do not know how to do this, you can refer to my guide or search the internet for instruction for your particular router.
NOTE: Do NOT block firs-ta-g7g.amazon.com as it is unnecessary for blocking updates and will cause problems during the initial setup if blocked.
Click to expand...
Click to collapse
Start enjoying your FTV as soon as you block those IP's correctly after verifying the FW you's came with...

Want to thank you both for good indepth responses.
I will be giving it a go tomorrow hopefully. Hoping that if i block updates for now then a root option may become available somewhere down the line, but till then i will enjoy the improvement of XBMC on the FTV rather than my rather slow raspberry Pi.
Many thanks guys

Just got an old Nook Simple Touch. Market not working. What can I do with it besides?

Ok, so I got an old Nook Simple Touch. In part because they can be had for such a cheap price on eBay these days and in part because they're among the few eInk based devices that run on Android and can actually be unlocked and more done with them than the manufacturers intended (I've used an old Kindle and man I hate how locked down and generally useless they are.) Actually, I was hoping I could do some neat stuff like setup daydream with weather info and a clock and all on it while the screen was "off" but I guess I forgot that this is a relatively new thing and it looks like it's based on a really really old Android version? Either way, I'm so used to CyanogenMod and its relatively near to AOSP nature that this thing is feeling horribly limiting and unpleasant to use for me.
Anyway, I've been searching around for various guides and such. I've found tools for rooting and putting the Google Market (yeesh, I forgot they used to call it "Market" ages ago.) It seems I needed to update the system to 1.1 for this (I had bootloops until I did, so clearly you have to have the right system version.) It seems there is a newer version or two beyond this though, but I didn't see root tools (I'm still hoping I can do more with this that might require root access to actually do.) Should I be updating beyond that? Namely, are there tools to actually root and all if I do?
Also, in the meantime, I'm running into troubles with the plain and simple fact that neither Google Market nor Amazon's app store installed by these tools work which may not be fixable. The thread on here says to add an account through Youtube first, then go to gmail and manually refresh over and over until it eventually crashes. After probably 15 minutes of this my hands were too tired to continue though. I just don't think it's supposed to take 15 minutes though. When I start the market it doesn't crash like that guide mentions either. Is there any other way to fix this? Is there any point? Obviously the market app is quite old, so perhaps it's simply never going to work? Is there some alternative way to find stuff that actually works on the NST? I thought to do F-Droid, but even it requires a newer SDK version apparently (I'm getting kind of curious what version of Android its base corresponds to. Does it predate 2.2? If so I may be in trouble since I don't think any of the stuff I was hoping I could put on there will go lower than 2.2.)
For this matter, is there a better way I can do stuff like loading apps? I was hoping to at least have a file manager to be able to use do stuff, but they didn't include one. I'll probably have to track down an apk. For now I'm having to actually use the network adb (I installed the version of the tools that was supposed to do adb over USB, but it doesn't even show up as an adb device at all for me to even so much as install a driver, so I guess it's not doing adb over USB as it should. The network method seems to work, though I'm not a big fan of leaving it wide open like that on principle really, yet remembering to manually change it on and off is a pain too.)
I realize this is a really old device and probably it is very limited what I can really do with it, but I was hoping I could at least squeeze a bit of use out of it. In particular, I'm going to need a much better reading app even if I use it for its intended purpose only. When I looked it up I had thought it was a close enough to stock Android that I'd be able to load up most apps I guess and I didn't think it would be so hard to even get anything on it.

Whew!
OK, let's start with basics. You didn't say how you rooted it but if you're working from 1.1 you probably are not getting the best out of the device. 1.21 is the final stock version. If you can get your NST back to stock, I would recommend doing so. Considering what you seem to have done already probably the easiest way to go is to use the NookManager route. Go here. Follow the instructions. There is info there for adding a Gapps package after rooting. But first get yourself back to 1.21 stock. Once that's done you can either use the Search Market tool from the Gapps package, or find apps on your computer and have them show up on the NST via the PlayStore, or side-load apps from the SD card or via ADB (default on that is WiFi with NookManager--you can install the ADB Konnect app and it works fine). There are plenty of alternate readers that run on the NST. I happen to like the stock reader very much, but to each his/her own.
When all that's done, everything depends on what your expectations are and what you want from your NST. There are a variety of kernals out there as well as USB host/audio mods. Although the Android system is old and the display limits what you can do, there are many apps that run well on the device and I personally get a lot of use out of mine, even more now that I have audio. Check out what I've done (second post) and look at what others have done (in the same thread).
There's a lot of good info in this forum on modifications, apps that run well (and don't) and many tips and tricks.

I think I have most of what I need with that actually, yes. I didn't realize from the guides I initially found that you could root or install third party components with a > 1.1 system version. With that stuff I do have a semi-working Google Market now and can actually install a lot more stuff than I thought. I see also my favorite reader app not only works, but apparently knows I'm running it on a device with an eInk screen and defaults to having eInk adaptations turned on.
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)

Nazo said:
Is there any way it can do anything like what I had sort of envisioned before btw? Eg on the screen "off" mode have some sort of thing that shows weather or news or something that updates every so often? (Nevermind the clock thing, that's probably a bad idea. I was just wondering about dedicating it to being sort of something like a clock with it plugged in all the time. Now I think maybe I can stop using my tablet for reading and use this instead.)
Click to expand...
Click to collapse
Sounds like you are having CM lockscreen widget withdrawal
Actually that seems like a job for Tasker. But it would be potentially messy. You'd need to:
1. Clear image in custom screensaver folder
2. Turn on wi-fi
3. Open weather/whatever app to update info
4. Take screenshot and save to custom screensaver folder
5. Close app
6. Turn off wi-fi
At that point when the Nook goes to sleep the info will be displayed on the lock screen. The question is whether Tasker can wake up the Nook and repeat this at desired intervals when you're not using it.
Also, have a look here for something along the same lines. Maybe you'll get an idea.

Ironically on my phone and tablet I keep it really simple. It's just that the eInk screen of the Nook can essentially be "always on" so to speak without draining the battery like mad (since it would only actually need to wake up every half hour or so for a frequent update schedule.)
But, all that said, it just doesn't sound like this is really worth all the effort. I guess I'm actually more used to newer versions of Android mostly rather than CyanogenMod specifically as they just have more power in what these things can do. With the Nook -- even unlocked and opened up -- it really sounds like the amount of time and effort required to even remotely approach such a thing is orders of magnitude higher. Well, that's fine. I had initially thought that I might maybe just use it as some sort of really neat "smart clock" type thing (at $35-ish on eBay you won't find many clocks that could come close to doing what an Android device could theoretically do) but in the end I don't think this is really all that realistic and definitely not worth the effort. On the other hand, now that I'm able to get more stuff actually running on it and open up its capabilities more I'm thinking I could maybe use this thing for something more akin to its original intended purpose: reading. From time to time I want my tablet to be able to do a bit more and I think this can do pretty well everything I care about beyond the basic reading stuff, so maybe I can stop carrying my tablet around all the time. (And for stuff like music I have a dedicated multimedia phone courtesy of eBay that's much better off really.)

My rooted unregistered Nook Simple Touch chews battery like crazy

I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!

Winston S. said:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Click to expand...
Click to collapse
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370

nmyshkin said:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
Click to expand...
Click to collapse
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.

Winston S. said:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Click to expand...
Click to collapse
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.

nmyshkin said:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
Click to expand...
Click to collapse
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!

Winston S. said:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Click to expand...
Click to collapse
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.

nmyshkin said:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
Click to expand...
Click to collapse
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:

Winston S. said:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
Click to expand...
Click to collapse
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life

nmyshkin said:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
Click to expand...
Click to collapse
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!
I'll be reading up on the way to get ADB working.
BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.
Thanks! :good:

@nmyshkin I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)
Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?
EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?
So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?
I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.

I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.

nmyshkin said:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
Click to expand...
Click to collapse
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.
I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.

Winston S. said:
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Click to expand...
Click to collapse
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.

nmyshkin said:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
Click to expand...
Click to collapse
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.
To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)

@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?

Winston S. said:
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Click to expand...
Click to collapse
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.

nmyshkin said:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
Click to expand...
Click to collapse
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!

Winston S. said:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Click to expand...
Click to collapse
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.

nmyshkin said:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
Click to expand...
Click to collapse
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.

Winston S. said:
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Click to expand...
Click to collapse
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/
Clearly that is bogus. So I checked out @wozhere's listed working version, or something close.
I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).
There were many more options on the version I once had, so this one is a starting point only.

Links to making a HD 10 into a Android clone or close to it. GPS question

Considering I was around PC's before dial up.... I've fallen way behind in the past few decades. So I was given a HD 10. It's great. But I'd like to download and use the android apps. Even the free ones will often say the app will not be fully utilized by the HD10. I had all this info from this site down loaded somewhere to be able to side load and do other stuff. Yes, I lost it. Sigh...
Hint: I have no idea what side-load is other than it sounds like a backdoor means to load software. So what I need if possible.
1. Link to instructions and programs that will allow the full use of the tablet as an android device if possible.
2. Can the HD10 be modified to work like a GPS that most smartphones and even cars now use? using Google maps and apps.
3. Any other tips or links for the HD10. I'm old, retired and have nothing but time. I've blown up my fair share of programs over the decades, so I'd prefer not to turn this "gift" into a target for when I go plinking. So if these programs have recovery options that'd be great. LOL!
Thanks.
BTW this site is terrific, I used it to unlock the Google play store. Great job.

Littlem56 said:
1. Link to instructions and programs that will allow the full use of the tablet as an android device if possible.
Click to expand...
Click to collapse
Follow the following instructions:
Unlock Bootloader & Root (required for 2nd)
Debloat (remove unnecessary Amazon apps)
There are some plans to port Stock Android, but it's still in progress.
Littlem56 said:
2. Can the HD10 be modified to work like a GPS that most smartphones and even cars now use? using Google maps and apps.
Click to expand...
Click to collapse
Currently no GPS, because Amazon didn't set it up right for some reason. AGPS (location service via network) works.

[Q] Fire HD8 (2018) w/ Play Store - app recognises it isn't Google, won't run.

The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?

Dyonas said:
The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Click to expand...
Click to collapse
Not easily. It would take experimentation to determine which device or rom characteristic(s) are trigging the behavior followed by additional fiddling to entice the app to run. Tethering that Nexus 7 to a slim power bank may be the best solution.

NEED ROOTED.
/system/build.prop
ro.product.brand = Amazon
ro.product.manufacturer = Amazon
Change to 'Google' or etc.
I think amazon is banned by the app.

The exact error message is "This app is only suitable for the Android platform."
Didn't see the pictures attached by @erono. If you root the tablet (or may be possible in temp root shell) and change the keys he mentioned, the app works after reboot.

Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!

Dyonas said:
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Click to expand...
Click to collapse
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.

nujak said:
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
Click to expand...
Click to collapse
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.

Davey126 said:
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Click to expand...
Click to collapse
Yeah, sorry I meant in specific context to having that particular app work on the HD 8 2018. Thanks to @erono (and testing it myself) Lanscape Magazine works with changing brand and manufacturer values in the BuildProp. I know it's possible and easy to do with root. I'm just not knowledgeable enough to know any other methods.

Method without root:
Use 'App Cloner (pro version)' create an cloned app.
You can modify MANUFACTURER and BRAND in 'Developer options -> Build props'.
App was modified, you can't update in Google Play Store or purchase any paid content.
This is not a good way.