• 4,430,900
    REGISTERED
  • 28,493
    ONLINE NOW

Posts Tagged: Amazon Kindle Fire

Kindle Fire For Dummies

Getting an Android tablet for the first time can be an overwhelming experience. Of course, users going to get an Android tablet already know that and accept the challenge, but that doesn’t stop users from having those first day jitters. Thankfully, XDA is not only a place of development, but also a place to learn for many users—especially ones new to Android itself.

Now, Amazon Kindle Fire owners have a great place to get started thanks to XDA Senior Member kinfauns, who wrote a tutorial that explains the basics of Android development and the Kindle Fire. The guide, which is a pretty long but rewarding read, runs users through a number of both Kindle Fire specific terminology and universal Android terminology. A list of the things that are explained include:

What is stock? What is rooting? What is a ROM?
What is a bootloader? What is a recovery?
What is fastboot? What is adb?
What is a bootmode? What is a bootloop?
What is a brick (hard-brick / soft-brick / unbrick)?
How do I unbrick my Kindle Fire?

Each section explains each concept very well and gives users links to the Kindle Fire development threads they pertain to. For first time Android users, new Kindle owners and even some intermediate users looking for a refresher course will all find a wealth of information in this overview. Additionally, for those who are looking for help can not only find a little info on how to fix, but the thread they can use to actually fix it. It’s a win win situation.

For more details, check out the original thread.

lockscreen

We’ve said it before, and we’ll say it again: touch-based recoveries are the future. Aside from giving end users easier access to device firmware modification, they add a much needed element of polish to the Android hacking experience. While some may say that these upgrade recoveries take away from the feelings of thrill and excitement, I argue that they offer a more efficient interface and enable some truly unique new features not available in the recoveries of yesteryear.

In a rather large update to what is arguably the most popular touch-based recovery around, XDA Recognized Developer Dees_Troy presents to us Team Win Recovery Project (TWRP, for short) version 2.1. Aside from simply bringing a friendly UI, TWRP 2.1 packs a healthy feature punch by offering zip queuing, a basic file manager, and dual storage support for backups.

TWRP supports scripting via a new scripting engine called OpenRecoveryScript for use with GooManager. With ORS, users can install multiple update.zip files from within Android, wipe cache & dalvik, and run a backup. Furthermore, in the name of openness, Team Win has submitted ORS as a commit to ClockworkMod.

In the words of the developer:

Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

New features for version 2 of the recovery software:

Zip queuing as seen in TWRP 1.1.x is back
Dual storage capable (backup, restore, and install zips from internal or external storage – you choose)
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added – Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme – makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI – makes all builds about 100KB smaller

If you’re itching to get started, please visit the development threads listed below. If instead you are looking to theme the recovery, visit their theming guide.

kindle-firefirefire

The Amazin Kindle Fire has proven itself to be a very popular and capable device. There is certainly no shortage of development for the device, much of which is listed in a very helpful thread posted by XDA Senior Member stiffmast3r.

Many people tend to immediately think of custom ROMs and kernels as the be-all and end-all of development that happens on XDA, and the bootloader of our devices is often overlooked. However this is not the case over in the Kindle Fire section. FireFireFire is a custom bootloader originally developed by XDA Senior Member pokey9000, which offers increased functionality over the stock bootloader in 3 ways:

  • It allows you to access recovery mode by simply pressing the power button again after the device begins to boot, thus negating the need for cumbersome button combinations.
  • It also automatically enables fastboot when the device is powered on, eliminating the need for idme bootmode, special cables or the command required by the stock bootloader on every run of fastboot.
  • It is also possible to use FireFireFire to repartition the devices memory and fix a bricked device when used in conjunction with ReKindle. (Be warned though that the method involves some AdamOutler style tinkering with the internals of your device)

Unfortunately it seems that pokey9000 is no longer working on FireFireFire. However, the modification lives on, and the torch has been passed to Senior Member kinfauns. His version brings a few changes that you may prefer to the original, namely a different boot logo and a shorter fastboot window which will shave 5 seconds off the boot time.

You can find both versions in the links below:

Factory Cable

Many Samsung devices can be placed into download mode using a USB Jig, which when plugged in, allows users to ODIN restore a factory ROM from what would normally be a hard brick.

Motorola devices and, as it happens, the Amazon Kindle Fire, have a similar option called the factory cable. The factory cable, as explained by the Team Black Hat:

Unlike a normal USB cable these cables are wired in a way that compatible Motorola phones recognize as a “factory” programming cable. This allows the phone to power up and be flashed without having a battery in the phone. Depending upon the model of the phone, it may also boot up differently than it does with a normal USB cable.

And, much like the Samsung USB Jig, it’ll help out those who have hard bricked their devices. XDA Senior Member SikYou has written up a brief explanation of the attempt made to create such a cable and from that has spawned an entire discussion, which slowly but surely details the full instructions to creating your very own factory cable. In his words:

There is a lot of information floating around about the factory cable but there doesn’t seem to be a thread dedicated to the topic. I bricked my device today so I need to make a factory cable. I tried making a cable but I f’d up the soldering job so I am awaiting delivery of a breakout board. I just wanted to gather some information here on the topic because there seem to be a lot of bricks popping up around here. So for now I am going to post what I know and ask a few questions here and there so that I can get my cable done and hopefully help someone out along the way.

With some contributions from several other XDA Forum Members, including MayfairDROID, pyrostic and teookie, the whole process is pretty much outlined for anyone who wants to give it a shot. However, it should be noted that an improperly made cable could damage your device. So proceed with the utmost caution if you intend on making one and, of course, it’s no one’s fault but your own if something goes wrong.

Head on over to the Amazon Kindle Factory Cable Thread for additional information and to get started. You may need to read a few pages in to get all the info, but it is all there.

Kindle Fire

As development for a popular device goes on, eventually users and developers will find new ways of performing already available tasks. Features of these new ways generally include features such as being easier to use, so the less tech savvy crowd can get in on the modding action and adding new options that are just really cool. Such is the case with a method posted by XDA Senior Member smirkis, which allows users of the Amazon Kindle Fire to install a custom recovery and a custom bootloader without using fastboot.

There are already methods that help users install a custom recovery and a custom bootloader. However, what sets this method apart is that it gives the user an option to choose which recovery and bootloader they install on the fly. And for users who have had enough with modifying their devices, there’s an option to return to stock bootloader and recovery. The full options include:

install clockworkmod touch
install firefirefire bootloader
Install new cwmtouch final by doomlord
Install new logo fff bootloader by kinfaun

The application comes in the form of an apk that users can install. From there, it’s just loading the scripts to install whichever bootloader and recovery you want and hitting go. It doesn’t get much easier than that.

You can find all the information, download links, and installation instructions you’ll need in the original thread.

Kindle Fire

One of the drawbacks to buying any device that doesn’t have Google Apps by default is the Android Market can be a little frustrating. Sometimes, not all the apps your device can run will show up. Other times, maybe apps you cannot run will show up. In any case, it can be a hassle.

For users of the Amazon Kindle Fire, your Market woes are one step closer to being over. XDA Member enkode has released a method that adds fixes to the Market so that Kindle Fire owners can have a more open experience with it.

The method itself is relatively simple, and easy to do as long as you follow the instructions. First, users are to edit their build.prop file and then install a modified version of the Android Market. The end result is Kindle Fire owners will have more Market goodness available to them than they had previously.

There are a few prerequisites though, to quote the developer:

YOU MUST BE RUNNING CM7
YOU MUST HAVE ROOT
I WILL NOT SUPPORT STOCK!

So you’re going to have to be rooted and running CyanogenMod before this mod will work for you. For those running the appropriate software, if you’d like to try it out, you can find the full instructions, download links and additional information in the original thread. As per the norm, be sure you make a backup before attempting, just in case something goes wrong.

kindlefire

Android tablets have increased their marketshare in 2011, from 29% in late 2010 to 39%, but not because of the strength of the Android ecosystem. Sure, us geeks like them for their powerful hardware, but most normal consumers are rather drawn to the Kindle Fire. The Amazon tablet runs a forked Android version, as we explained earlier, and has proven to be extremely popular. Even though there are still more Galaxy Tabs in the wild, the Kindle Fire already sees the same amount of user engagement.

The data from Flurry, a mobile analytics provider, shows that both Kindle Fire and Galaxy Tab are now responsible for 36% of all application sessions, defined as “the launch and subsequent exit (or pause for more than 10 seconds) of an app”. Compare that to last November, when 63% of all application sessions were tracked on the Galaxy Tab – the Fire, which only launched at that time, was at a mere 3%.

While impressive, this does not mean that the Kindle Fire already caught up in terms of marketshare. Due to a headstart of more than a year, Flurry estimates that the number of active Galaxy Tabs is still over twice as much as that for the Kindle Fire. However, this makes the above statistics even more impressive – clearly, those who own a Kindle Fire use it much more frequently than those who own other Android tablets.

Kindle Fire owners are also much more willing to buy apps, as they download over 2.5 times as many paid applications through the Amazon Appstore than Galaxy Tab owners through the Android Market.

In the end, while ‘traditional’ Android tablets do offer a lot of functionality, they haven’t really caught on in the marketplace, nor are they being used as much as other tablets. While one might have speculated that many only bought the Kindle Fire because of its extremely low price, without actually using it a lot, these numbers tell a different, and rather troubling, story. At least for Google.

Read the full report at Flurry.

kindlefire

What seems to be the most popular Android tablet out there right now, Amazon’s Kindle Fire, has received an OTA update starting a few days ago. As always, it initially broke root access, but our forum members have already found a workaround for that. So, there’s no point trying to prevent it now, else you won’t get the following features:

This update enhances fluidity and performance, improves support for manually set up e-mail providers in the Email app, and offers a new full screen mode for viewing web pages.

If you’ve already received and installed the OTA update, use BurritoRoot by recognized developer jcase, who has updated his tool to work with the new 6.2.2 version, to regain root. If not, then head over to this forum thread to download the pre-rooted update package flash-able with TWRP, courtesy of forum member nfinitefx45.

461391997

XDA Senior Member Azdian has developed a nice little mod that will add RTL (right to left) language support for Amazon Kindle Fire users.

The process is a little complicated and involves switching out a few lib files. So if you’re not confident with fiddling with the framework of the device, make sure you do some homework and get comfortable with it before attempting as messing up can damage your device. Be sure, as always, to perform a full back up just in case.

The process is otherwise not complicated, as Azdian says:

*Download Madmack RTL Patacher HERE, then extract the files, you will see some subfolders and files what you need to remember is input and output subfolders and command.exe for later use.
*Go to your kindle open Root Explorer [or any app can do the same] and copy these files from your kindle to your pc
*move these files to input subfolder , and then run commands.exe DO NOT close the black cmd screens that will pop up, wait till its finish, once its done you will find these files in the output subfolder

So if you’re of the Arabic, Persian, Hebrew, etc persuasion and want the RTL support on your Kindle Fire, you can find the download links, the complete instructions and further information in its original thread.

kindle

For those who don’t like Windows, we’ve already told you about Firekit LiveUSB Repair Kit, but if you do like Windows, there’s now a way to fix your Amazon Kindle Fire.

XDA Member Zombiepiratez has created a helpful little program for Windows that will help you fix the brick. It runs in Windows Command Prompt, so the UI is dead simple to use and the selections are easy to understand, so noobs need not fear in terms of difficulty. Unfortunately, Zombiepiratez has sustained personal injury, as he says:

Unfortunately, I have broken/sprained my wrist, and am unable to move my fingers without a fairly great amount of pain. This is only my right hand, but sadly, I am right-handed. For the next month, I will be unable to code, meaning no new versions or bugfixes.

So, if you find a bug, feel free to report it and don’t get discouraged if you don’t hear back.

For more information, download links and screen shots, check out the original thread.

iu_Xpl5DLCOM

Sometimes, Windows just doesn’t cut it. Many developers use some distro of Linux for most of their work and, while better off than most Mac users, Windows has the capacity to cause mammoth headaches.

This is especially true for some Amazon Kindle Fire owners, who’ve reported having trouble with ADB and Fastboot drivers on Windows.

To rescue comes XDA Senior Member pokey9000 who has devised a method for getting around this and restore Kindle Fire owners to their headache free ways. He explains what it is exactly:

Firekit combines all the command line tools for Kindle Fire recovery with the Ubuntu LiveUSB. All you need is a USB stick and a PC that can boot off it. All files stay on the stick, so nothing on your PC is changed.

While this will require a little know-how about creating Ubuntu LiveUSB, once you get passed that, it’s a relatively simple process. After you create your Ubuntu LiveUSB and get the files on there, you can use the command line to do anything from restoring your Fire to fixing messed up partition tables. Here’s a full list of the commands (to be entered in the command line):

install_fff_twrp_from_stock: Install FFF and TWRP while in stock Android. Uses fbmode to reboot. Use this to get FFF/TWRP installed on 6.2.1 stock OS.
install_fff_twrp: Install FFF and TWRP while in fastboot. Good if you’re stuck in fastboot and you want FFF/TWRP.
fix_parts Restore partition table to stock while in fastboot. Do this if you’re in fastboot and your partition table is screwed up.
normal_boot: Set the bootmode to boot android and reboot while in fastboot. Try this if you’re stuck at the Kindle Fire logo.
usb_boot_twrp: USB boot TWRP without installing. Boot TWRP if your Kindle black screens when you try to power it on. Needs the USB boot mode trick.
usb_install_fff_twrp: USB boot FFF, install FFF and TWRP. Install / recover the bootloader and recovery if they are broken. Needs the USB boot mode trick.
usb_fix_parts_and_install_fff_twrp: USB boot FFF, restore partition table to stock, install FFF and TWRP. Fix everything if you screwed up the partition table and your Fire’s screen no longer turns on. Needs the USB boot mode trick.

If this powerful alternative to trying to get things to work via Windows is something you would like to check out, you can check out the original thread for additional instructions, a tutorial on its use and download links. It seems that pokey9000 is also planning to do more support for this, as he does have a to-do list at the bottom of the first post for things he intends to fix and improve on.

10811486_img_20120101_113457

We all knew it would be happening soon, as the AOSP ROMs are essentials for most new phones and tablets and the Amazon Kindle Fire is the latest and greatest device that MIUI calls home and the development of the Amazon Kindle Fire remains on fire (bad pun ftw!).

XDA Senior Member leech2082 released the port which, for a first release, has a surprisingly low number of things not working in comparison to most ports that make first appearances on devices. According to him:

Everything seems to be working except MIUI Themeing and Video! Certainly you guys will find something I missed

So if MIUI theming and video are a couple of things you can live without and MIUI is something you’ve been waiting for, then now would be a great time to check it out. The installation instructions are easy and pretty standard for a ROM flash. Boot into recovery, wipe everything, flash and profit.

The boot up can take a few minutes, and as leech2082 will tell you:

what i have found is the boot animation may cycle twice before fully booting. Also after flash when you hit reboot sometimes it brings up the TWRP screen again. If that happens just hit reboot. Since there is not hard buttons on kindle we included Button Savior you will see if on the right side of screen by default

Not a big deal and easily fixable so nothing to be scared of and no reason not to take advantage of the always fun MIUI goodness. For more information, the shout outs, download links, screenshots and more thorough instructions, feel free to mosey on over to the original thread.

kf_ics_02

For those of you who don’t fancy running Amazon’s heavily modified Android version, even with root, there’s a new option on the horizon: Android 4.0 Ice Cream Sandwich. After forum member g1011999 manged to get it booting three weeks ago, JackpotClavin, who’s also responsible for the Kindle Fire’s CyanogenMod 7 port, has posted a working build that he says isn’t even alpha.

So, unless you want to help on the development or are really curious (we know you are), we’d suggest you to wait for a more stable version. For everyone else, head over to the forum thread to get downloading and flashing.

Image credit: Liliputing

Advertisement

XDA TV: Most Recent Video

Upcoming Devices

  • Samsung Galaxy S III Q2
  • Asus Transformer Pad Infinity Q2-Q3
  • LG Optimus X4 HD Q2-Q3
  • Sony Xperia Ion Q2-Q3
  • Toshiba Excite 7.7, 10, 13 Q2
  • Device names link to XDA forums when available.
Advertisement