How To Install Ice Cream Sandwich On Your Kindle Fire
#1
Posted 01 July 2012 - 05:01 PM
#2
Posted 02 July 2012 - 02:38 AM
#3
Posted 02 July 2012 - 06:42 AM
#4
Posted 02 July 2012 - 09:26 AM
#5
Posted 02 July 2012 - 11:14 AM
#7
Posted 03 July 2012 - 05:56 AM
First, I couldn't get the Kindle Fire utility to install in Windows 8 at all. So, I found a Windows 7 system and it worked fine.
But, Step 2--Switch to Fastboot Mode--isn't working. It just tells me that "adb" is not a recognized command line option.
I did some searching online and found a suggestion that I need the Android SDK installed, so I downloaded that. But, it wouldn't install because it said I need the Java Development Kit installed. So, I downloaded and installed the JDK--but the Android SDK installation still claims I don't have the JDK and fails.
And that brings me to now--where I wonder if all of this effort is worth it. Or, what do you do when there are updates to Android and you have this hobbled together, rooted device that takes five different pieces of questionable third-party software to make it work. Will I have to go through all of this craziness every six months when new updates are available?
PCWorld Net Work Blogger
Email: tbradley@pcworld.com
Twitter: TheTonyBradley
Facebook: Join the Page
#8
Posted 04 July 2012 - 03:15 PM
boomer1204, on 02 July 2012 - 06:42 AM, said:
How do you do all that you just talked about?
Thank you.
#9
Posted 04 July 2012 - 06:24 PM
Russellt1ro, on 04 July 2012 - 03:15 PM, said:
boomer1204, on 02 July 2012 - 06:42 AM, said:
How do you do all that you just talked about?
Thank you.
I had to change directories to the following directory in cmd before running any command with adb - C:\Program Files (x86)\Android\android-sdk\platform-tools. I hope that helps.
#10
Posted 05 July 2012 - 10:58 AM
#11
Posted 05 July 2012 - 02:42 PM
meier2k8, on 05 July 2012 - 10:58 AM, said:
Nevermind, I've fixed the problem and now have a beautiful Kindle Fire running Ice Cream Sandwich! Finally figured out the issue with the adb, noticeably occurring from a lack of guidance on the part of the instructions posted here at PC World.
However, the rest of the guide was a breeze to use, great job!
#12
Posted 05 July 2012 - 11:32 PM
#13
Posted 05 July 2012 - 11:33 PM
#14
Posted 05 July 2012 - 11:59 PM
NithinORajan, on 04 July 2012 - 06:24 PM, said:
Russellt1ro, on 04 July 2012 - 03:15 PM, said:
boomer1204, on 02 July 2012 - 06:42 AM, said:
How do you do all that you just talked about?
Thank you.
I had to change directories to the following directory in cmd before running any command with adb - C:\Program Files (x86)\Android\android-sdk\platform-tools. I hope that helps.
No, sorry i still have no idea what you're talking about
#15
Posted 06 July 2012 - 05:53 AM
1. You have to download/install the Android SDK before 'ADB' commands will be recognized. After downloading you will need to start the Android SDK Manager and install the 'Android SDK Platform-tools'.
2. At the command prompt you'll have to navigate to the folder where you install the SDK tools in order for the ADB commands to work. The folder will be: Android\android-sdk\platform-tools. If you installed the SDK for all users, the above folders should be in C:\Program Files (x86)\. If you installed just for the current user it will be in C:\Users\USERNAME\AppData\Local where USERNAME is the username you installed it to.
Good luck
#16
Posted 06 July 2012 - 08:30 AM
WebsterMiller, on 06 July 2012 - 05:53 AM, said:
1. You have to download/install the Android SDK before 'ADB' commands will be recognized. After downloading you will need to start the Android SDK Manager and install the 'Android SDK Platform-tools'.
2. At the command prompt you'll have to navigate to the folder where you install the SDK tools in order for the ADB commands to work. The folder will be: Android\android-sdk\platform-tools. If you installed the SDK for all users, the above folders should be in C:\Program Files (x86)\. If you installed just for the current user it will be in C:\Users\USERNAME\AppData\Local where USERNAME is the username you installed it to.
Good luck
what do you mean navigate to that folder? do you just type the folders address into the command prompt?
#17
Posted 07 July 2012 - 07:25 AM
JustinHaddock, on 06 July 2012 - 08:30 AM, said:
WebsterMiller, on 06 July 2012 - 05:53 AM, said:
1. You have to download/install the Android SDK before 'ADB' commands will be recognized. After downloading you will need to start the Android SDK Manager and install the 'Android SDK Platform-tools'.
2. At the command prompt you'll have to navigate to the folder where you install the SDK tools in order for the ADB commands to work. The folder will be: Android\android-sdk\platform-tools. If you installed the SDK for all users, the above folders should be in C:\Program Files (x86)\. If you installed just for the current user it will be in C:\Users\USERNAME\AppData\Local where USERNAME is the username you installed it to.
Good luck
what do you mean navigate to that folder? do you just type the folders address into the command prompt?
When in command prompt - and assuming you have downloaded the Android SDK with ADB packages - begin with "cd c:\program files\android\android-sdk\platform-tools\"
This is was the method that I had to use to get the ADB commands to work, and that's assuming that Android SDK is located in your Program Files of your C: drive. Once you are within that directory, they you can begin executing the ADB commands from the PC World instructions. I just went through the pain of all this a couple days ago doing the exactly what had happened to you and had to learn the hard way over the course of a few hours.
#18
Posted 07 July 2012 - 09:37 AM
tonybradley, on 03 July 2012 - 05:56 AM, said:
First, I couldn't get the Kindle Fire utility to install in Windows 8 at all. So, I found a Windows 7 system and it worked fine.
But, Step 2--Switch to Fastboot Mode--isn't working. It just tells me that "adb" is not a recognized command line option.
I did some searching online and found a suggestion that I need the Android SDK installed, so I downloaded that. But, it wouldn't install because it said I need the Java Development Kit installed. So, I downloaded and installed the JDK--but the Android SDK installation still claims I don't have the JDK and fails.
And that brings me to now--where I wonder if all of this effort is worth it. Or, what do you do when there are updates to Android and you have this hobbled together, rooted device that takes five different pieces of questionable third-party software to make it work. Will I have to go through all of this craziness every six months when new updates are available?
I'm with you. I have complained to those that write such tutorials as they simply assume way too much. I too don't have any such tools on my PC and why would I? It always amazes me that YouTube videos and other tutorials about how to hack Android are so worthlessly written.
Amazon Kindle Fire HD | Nokia Lumia 920
#19
Posted 11 July 2012 - 02:13 AM
meier2k8, on 05 July 2012 - 02:42 PM, said:
meier2k8, on 05 July 2012 - 10:58 AM, said:
Nevermind, I've fixed the problem and now have a beautiful Kindle Fire running Ice Cream Sandwich! Finally figured out the issue with the adb, noticeably occurring from a lack of guidance on the part of the instructions posted here at PC World.
However, the rest of the guide was a breeze to use, great job!
Hi there,
I'm the author of this guide, and I tested the procedure myself (with my own Kindle Fire and computer) before writing it up, and wrote it based on instructions I found on XDA that had lots of positive reviews. Reading the comments, it's obvious there was a missing piece relating to ADB. This may be because it was previously installed on this computer, and the original instructions did not cover it (and worked as written).
Would you mind telling me how you fixed the problem? I would like to revise this how-to to include the info about ADB.
#20
Posted 19 July 2012 - 08:51 PM
Help













