#otter2

[arthur-cohen]

@just-your-insignificant-otter

“Hey there, stranger,“ Arthur slumped down beside Otter on the dock. He set down a bottle of light beer by her leg and then offered her a stick of freshly toasted marshmallows,” This is for you.”

[enembydev]

How to replace the OS on a Kindle Fire 2 (Master Guide)

I recently found and bought a Kindle Fire 2 for $13 at a thrift shop. I had originally thought it was a more modern device, and when I powered it on I found that it barely functioned at all, since a factory reset had removed access to the amazon store and changes to the login process on amazon made it impossible to normally log in and download apps.

So I set my sights on rooting and reinstalling the thing, and boy it was an adventure. Almost all of the resources for this are now gone, having mostly been made around 2012, and putting together everything necessary took nearly a full day of browsing the XDA forums. So for future searchers, here's a full guide to installing LineageOS on a Kindle Fire 2 (commonly called the Otter 2) using Windows 10:

You will need:

Google's SDK Platform Tools

Minimal ADB and FastBoot (this is technically not neccessary, but I couldn't get regular fastboot working on my machine 100%).

Every file mentioned in this github guide.

If anything linked is not available, I'll have a full mirror linked at the end of this post.

Make sure that adb is installed and working, by plugging in your kindle and typing "adb devices" into a command prompt. If it doesn't immediately work, try reinstalling based on this guide in Windows Device Manager.

Once adb is definitely working, follow all steps in this Github Guide.

You'll need to root, and with the stock tablet, which has no access to a file manager this is impossible to do without an external device. I used Kingoroot, the desktop version. Keep in mind KingoRoot does install some basic adware, but windows 10 can detect and remove it easily.

If you're like me, once you reach the fastboot section, every command attempt leaves out errors. At this point, navigate to the folder of the Minimal ADB and Fastboot programs installed earlier. Open it in command prompt. You can do this quickly by typing cmd into your file explorer.

Then in these folders, try running the fastboot commands again. This will instead use minimal fastboot, which for some reason works while official tools don't.

Then you need only follow the rest of the Github Guide, making minor changes in the filenames depending on what you downloaded.

Mirrors:

Mediafire

MEGA

Google Drive