That being said: a lot of the instructions are videos and sometimes I like to have just a simple text document to follow (especially when it comes to rooting). You can view their videos here on YouTube.
The awesome people over at RootJunky have developed a tool specifically for the Kindle Fire 5th gen to get a bunch of features that you normally wouldn’t have access to. Well, what else can we do? Lots, as it turns out. Unfortunately, the support for this model is fairly lacking at the moment (I only found 2 ROMs: Slim ROM and CM12.1 I tried both and they were both a little lacking between bugs and missing features Update: as of 3/7 RootJunky has shown AOSP to work pretty well on Kindle Fire 5th Gen, I will need to do independent testing to confirm this). I’ll turn this $40 device into something really powerful and useful. I do it on my personal phone all the time: Custom ROM. I spent a lot of time trying to research what I could do about this, and it came down to something fairly simple. No Google Play Store (instead Amazon App Store, which has less apps and apps which are free on Google Play Store cost money on the Amazon App Store).🙁Īfter about a month of using it I started getting some very frustrating behaviors from the stock Kindle interface (a HEAVILY modified and locked down version of Android OS called FireOS): If you cannot find the drivers in the path it is because of an issue outside of my scope of ability to look into - it is likely a change in Windows. I have confirmed this on the latest build of Windows 10 – I did not create the drivers, I merely wrote a guide for doing the steps because I was tired of watching videos for things that could be simple words.
IMPORTANT NOTE: A lot of users are mentioning that they can’t find the drivers in the specified path anymore. For what I paid for it ($40 or so) I couldn’t be happier. I love reading (both books and magazines) and honestly: it’s a super convenient little tablet. Recently I picked up a Kindle Fire 7″ 5th Gen from Best Buy because they were on sale.
0 kommentar(er)
