[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]2nd generation Kindle Fires[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How can I tell if I have a 2nd generation Kindle Fire?[/SIZE]For HD models the answer should be pretty obvious, but the KF2 has nearly the exact same hardware configuration as the original. Short of opening the device, the only way to tell for sure is by checking the software version. Devices running a software version of 6.3.2 or earlier is a 1st generation Kindle Fire. All other versions belong to 2nd generation Kindle Fires.[SIZE=+1]Q2: What is the most important thing to know about the 2nd generation Kindle Fires?[/SIZE]The 2nd generation Kindle Fires are running on OMAP4 HS processors with “M-Shield” turned on. What that means is ANY alteration to certain partition images containing digitally signed headers (with one exception) will result in the OMAP ROM halting the boot process and the resulting “brick” will be irreparable by anyone but Amazon. For more information, or just for an interesting read, go here: New Kindle Fires are locked[SIZE=+1]Q3: What partition images contain these signed headers?[/SIZE]The xloader, bootloader, recovery, and boot (kernel) partition images all have signed headers. Any attempt at installing custom versions of these partition images by means of traditional methods to modify the device will result in the aforementioned irreparable “brick”.[SIZE=+1]Q4: How do I create a partition image with a signed header that can be used on the 2nd generation Kindle Fires?[/SIZE]You can't. Ignoring the fact that the signed header must have the exact same 64Kb signature that Amazon uses in the factory, the software used to produce this signature is not available to the general public, but only to “high volume wireless OEMs and ODMs”.[SIZE=+1]Q5: You mentioned “one exception” to installing custom partition images? Could you elaborate on this?[/SIZE]While the “M-Shield” technology for OMAP HS processors is pretty robust, the same ccouldn't necessarily be said for Amazon's software. The stock Kindle Fire bootloaders from software updates previous to 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) have an exploitable hole in the boot process which allows the installation of a 2nd bootloader (on the system partition) and unsigned custom recovery & boot (kernel) images, without much fear of doing irreparable harm, but the actual bootloader must still remain stock. It should be noted that stock Kindle Fire bootloaders since the 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) updates have this hole patched and any attempt to install the 2nd bootloader along with unsigned recovery & boot images WILL BRICK THE DEVICE.[SIZE=+1]Q6: How will I know what version of the stock bootloader is installed on my device?[/SIZE]There is no way to confirm with all certainty what bootloader version is installed on the device, but a very good indicator to look for is the software version itself. Software versions prior to 8.1.4 (KFHD8.9), 7.2.3 (KFHD7), and 10.2.4 (KF2) have bootloaders that can be exploited. Everything beyond that must be replaced with one from a previous software update version. [SIZE=+1]Q7: My device is running a software version with a stock bootloader that cannot be exploited (or I am not sure). How can I install the 2nd bootloader for running custom ROMs and recovery?[/SIZE]Use fastboot to flash a signed stock bootloader from a previous software version. It should be noted that this is very risky to do. Sudden losses or surges of power, accidental unplugging of the USB cable, or flashing a bad download can potentially brick the device, for good. Always check md5s on all bootloader downloads, make sure you have a good charge, and keep all small children at a respectable distance. [SIZE=+1]Q8: Where can I find the 2nd bootloader and information on how to install it?[/SIZE]
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 8.9”
[BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
[BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2
[SIZE=+1]Q9: What can I do to restore my device if the 2nd bootloader and custom recovery is not installed?[/SIZE]Use fastboot to restore saved partition images from or for your particular device.[SIZE=+1]Q10: How do I save my partition images to restore later if needed?[/SIZE]For HD models, there is a script created by kinfauns that will do the work for you, but it will not work properly for the KF2 if the partition layout isn't the same. Regardless of what device you own, this can easily be done on any rooted device using 'dd' to save those partitions to the sdcard, then transfer them to your computer:
Code:
adb shell su -c “dd if=/dev/block/mmcblk0pX of=/sdcard/<filename>.img”
...where 'X' will be a number 1-13 (depending on partition layout) and '<filename>' will be the name of that partition. You can get a list of partition names and corresponding numbers with the following command:
Code:
adb shell su -c “ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name
Use 'adb pull...' to transfer the images to your computer for safe keeping, and avoid trying to save the userdata or sdcard partitions.[SIZE=+1]Q11: How do I restore a saved partition in fastboot?[/SIZE]
Code:
fastboot -i 0x1949 flash <partition_name> <partition_name>.img
...where '<partition_name>.img' should be the full path to the appropriately named partition image located on your computer. [SIZE=+1]Q12: Where can I get saved partition images for my device if I haven't previously saved them myself?[/SIZE]
[BACKUP][RECOVERY] Kindle Fire HD and 2 First Aide Software
[SIZE=+1]Q13: How do I restore my device if the 2nd bootloader and custom recovery is installed?[/SIZE]Generally speaking, most any problem can be resolved by reinstalling a ROM while being sure to wipe data (factory reset) first.[SIZE=+1]Q14: How will I know if I have a bricked 2nd generation Kindle Fire that cannot be restored?[/SIZE]The device will not show any outward signs of life; no display, no sound, and no LED. The device may still get warm when plugged in or turned on and Windows users may see an OMAP4 device in the device manager. Again, short of sending it back to Amazon, there isn't anything that can be done. [SIZE=+1]Q15: What about the 'usbboot' method used on 1st generation Kindle Fires for replacing a malfunctioning bootloader? Could something similar be implemented for 2nd generation Kindle Fires?[/SIZE]Not likely. The 'usbboot' method used to install the xloader, bootloader, and custom recovery on the 1st generation Kindle Fires is different for 2nd generation devices. The most significant difference being the USB loader used to initially flash these images must also have a digitally signed header. As explained by Pokey9000, short of finding an exploit in the OMAP ROM code (unlikely) or somehow acquiring the appropriately signed USB boot tools used by Amazon to flash the bootloader in the factory (even less likely) it will probably never work.[SIZE=+1]Q16: How will I know if my 2nd generation Kindle Fire can be restored?[/SIZE]Generally speaking, any device that will power on and show at least something on the display, will give you access to fastboot, thus the ability to restore saved partition images, and in effect the device. Many times this will require the use of a factory cable, so in some cases, owners of the KFHD8.9 will be out of luck.[SIZE=+1]Q17: How can I access fastboot mode on 2nd generation Kindle Fires?[/SIZE]There are 3 methods currently used for accessing fastboot mode on the 2nd generation Kindle Fires. Depending on the model, one or more of these methods may not work.
For all devices, entering “reboot bootloader” in the shell as the root user should reboot the device into fastboot mode.
On HD models, entering a fastboot command that waits for a handshake from the device (i.e. <waiting for device>”) such as “fastboot -i 0x1949 getvar product” and rebooting the device will usually enable fastboot mode when the device reboots.
On the KFHD7 and KF2, a factory cable can be used to access fastboot mode by plugging it into the device after it has been powered down.
[SIZE=+1]Q18: My device, when booted, displays a red or orange screen and does not respond to fastboot commands. What happened?[/SIZE]You probably tried to install the 2nd bootloader and custom recovery without making sure the bootloader you're running is the the unpatched version from a previous update. The red screen, or “Wall of Fire” as Amazon calls it, is displayed when the digital signatures don't match, as would be the case when installing custom recovery on a device with a patched bootloader. A factory cable is needed to get into fastboot so those partitions can be restored to the original signed versions. Since the factory cable doesn't work on the KFHD8.9, owners of these devices may be out of luck. [SIZE=+1]Q19: What is a factory cable? What is it used for? How do I use it?[/SIZE]A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the some devices, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a your device once it has been powered down.[SIZE=+1]Q20: Where can I find information on making or purchasing a factory cable?[/SIZE]
[Info]Making/Using a Factory Cable
SkOrPn
[SIZE=+1]Q21: How will I know when my device is in fastboot mode?[/SIZE]It will say “Fastboot” on the display[SIZE=+1]Q22: I have access to fastboot mode, but fastboot commands won't work (prompt sits at <waiting for device>). What's wrong?[/SIZE]Your USB/device drivers aren't configured properly.[SIZE=+1]Q23: Where can I find information on how to properly install the drivers?[/SIZE]
[GUIDE] Kindle Fire For Beginners – Post #2
Let's take some of the mystery out of getting ADB working in Windows
Note: While those tutorials are made for the original Kindle Fires in mind, the information is still the same in regards to installing and configuring USB device drivers.[SIZE=+1]Q24: I've read all the tutorials and tried various different tools, but I'm still unable to get my drivers working properly. What else can I try?[/SIZE]
SoupKit
[SIZE=+1]Q25: Now that I know all of the important stuff, how do I root my 2nd generation Kindle Fire?[/SIZE]While there are several tools and scripts used to root the 2nd generation Kindle Fires, they all rely on the same basic method, the Bin4ry method , which takes advantage of a remount timing issue during an ADB restore. It is very effective and works for nearly all devices natively running Ice Cream Sandwich.
Note: Despite some of the rumors about using your Amazon account password as the encryption password, this is a misconception. No password is needed because none was set.[SIZE=+1]Q26: Where can I find information about how to install Google Play on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version
[SIZE=+1]Q27: Where can I find information about how to install Google Apps on the stock OS?[/SIZE]
[ROOT][HOW TO] Install Google Apps with Speech Recognition Noob (Simple) Version
*Forum Rules | New Users Guide | XDA Tour | Report PostsThis FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
Excellent idea! Please sticky. :thumbup:
This is a Kinology HD using XDA Premium
What's funny to me is that people still get confused that their KF2 are NOT the same as a KFHD7.
It is understandable, of course, because they look the same on the outside and to a general consumer who lacks the knowledge of software can easily confuse the two, however, it must be made clear in some way, or otherwise we get more cases where people with a KF2 flashes a KFHD7 bootloader and such.
However, if you're going to venture so far as to void your warranty and get yourself involved with things like ADB, Fastboot, and Bootloaders where warnings and BIG bold RED letters , you should first know what model you have and what types of posts are designed for your device. Not to be mean, just saying. It would save you a ton of time and trouble, and not have a paperweight on your hands. Know what you're doing, and what you're getting yourself into, and you'll be just fine.
Super useful information, Thank you Soupmagnet. :good:
Too bad the Thanks button can only be pressed once!
+1
NY K2nd Ed is running very slowly. I clear the browser, but that doesn't help at all. Any suggestions?
It should be noted that stock Kindle Fire bootloaders since the 8.3.0 (KFHD8.9), 7.3.0 (KFHD7), and 10.3.0 (KF2) updates have this hole patched and any attempt to install the 2nd bootloader along with unsigned recovery & boot images WILL BRICK THE DEVICE.
Click to expand...
Click to collapse
So does that mean all bets are off ? Any 7" KFHD that has been updated to 7.5.1 will remain a useless stock device?
Any help with a bricked HD 7? It's stuck at fire logo. Can't find anything good. It's all outdated posts/articles by like 6 years
Related
Hi all
I have a new Kindle Fire HD 7". According to 'About' it's version is 7.3.1. The model number on the back is X43Z60
I've read just about every thread in this forum about rooting, flashing recoveries, using adb, fastboot etc etc.. I even made my own factory cable. I have been successful in rooting the device, I can access it via adb with no issues and I have even managed to install SafeStrap on it (though no ROM's will install) but I can NOT get it to boot into fastboot mode. I have successfully written to the idme bootmode 4002 and rebooted it but it has no effect. Windows does not detect any device other than the adb interface at any point. I even tried this while booted into safestrap and it too had no effect.
I'd like to know if anyone is able to say definitively what it is I need to do to get a custom ROM working. It doesn't help either that people seem to refer to the devices they have written their software for simply as "Kindle fire HD 7" with no mention of version, etc. meaning I have little indication as to the suitability of the instructions.
I saw mention of a 'short' mod where I am able to take the cover off and short a particular exposed connector to the frame and enable fastboot mode, but couldn't actually find any further information. Not afraid to give it a go but I need to know what to do.
Any help is appreciated
Thanks
A fast boot cable just puts five volts on pin 4 on the micro usb...that's the short mod....you short the five volt pin 1 to pin 4...note this has to be on the micro usb side you will blow up your usb port if you do it on the usb end
Safe strap is not the route you want to take I would at this point restore back to stock and install twrp as your second boot loader then installing a Rom should be simple
Sent from my GT-P3110 using xda app-developers app
TimTams said:
Hi all
I have a new Kindle Fire HD 7". According to 'About' it's version is 7.3.1. The model number on the back is X43Z60
I've read just about every thread in this forum about rooting, flashing recoveries, using adb, fastboot etc etc.. I even made my own factory cable. I have been successful in rooting the device, I can access it via adb with no issues and I have even managed to install SafeStrap on it (though no ROM's will install) but I can NOT get it to boot into fastboot mode. I have successfully written to the idme bootmode 4002 and rebooted it but it has no effect. Windows does not detect any device other than the adb interface at any point. I even tried this while booted into safestrap and it too had no effect.
I'd like to know if anyone is able to say definitively what it is I need to do to get a custom ROM working. It doesn't help either that people seem to refer to the devices they have written their software for simply as "Kindle fire HD 7" with no mention of version, etc. meaning I have little indication as to the suitability of the instructions.
I saw mention of a 'short' mod where I am able to take the cover off and short a particular exposed connector to the frame and enable fastboot mode, but couldn't actually find any further information. Not afraid to give it a go but I need to know what to do.
Any help is appreciated
Thanks
Click to expand...
Click to collapse
Visit the thread in my signature for the Kindle Fire HD 7". I addressed the issue of Amazon OS 7.3.1 with Step 1: Rooting.
Thanks for the info about the cable, ended up not needing it
seokhun said:
Visit the thread in my signature for the Kindle Fire HD 7". I addressed the issue of Amazon OS 7.3.1 with Step 1: Rooting.
Click to expand...
Click to collapse
Thanks!! I must have overlooked your guide, the titles of a few threads are very similar
Yours is the only one that didn't require the use of fastboot to get TWRP on the device, it worked flawlessly!
Cheers
One very happy TimTams :laugh:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.
Fastboot cable works just fine with the one I have.
Hello, I'm new to the Fire HD 7 but not new to XDA. I just got my wife the Fire HD 7, which has 7.4.8 on it. I would like to change it over to probably CM10, however I don't seem to have much luck finding clear instructions to first downgrade to 7.2.3. I'm pretty sure from there I can get it well enough, but getting it to downgrade is eluding me - I've tried from both my Windows 7 workstation and my Windows 8 laptop.
Any assistance would be greatly appreciated.
Thank you!
There's no need to downgrade the os technically, just make sure you have the ROM on it first, also I recommend cm 11, it's newer and uses less ram. Lemme link you to a tutorial for your device and give you some hints.
http://forum.xda-developers.com/showthread.php?t=2271909
Ok thats the tutorial, it tells how to back it up and such as well which I recommend. This method uses an app called fireflash to install 2nd bootloader + twrp. This process requires root BTW so if you haven't done that then uh here is a rooting tool. Now there is one step in the process I must warn you is very important that so many people overlook, when running fire flash you should see red warning text about the bootloader not being old enough to work and that it needs to be downgraded, there is a checkbox for doing this either above or next to the red text, if you don't check this and you hit flash you will reboot with a red screen you can't fix without a fastboot cable. Also like I said get the cm 11 ROM from here, and grab the corresponding gapps and stick them both on the sdcard ahead of time or you will be having fun using adb commands to push it to the device as it will bootloop.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
There's no need to downgrade the os technically, just make sure you have the ROM on it first, also I recommend cm 11, it's newer and uses less ram. Lemme link you to a tutorial for your device and give you some hints.
http://forum.xda-developers.com/showthread.php?t=2271909
Ok thats the tutorial, it tells how to back it up and such as well which I recommend. This method uses an app called fireflash to install 2nd bootloader + twrp. This process requires root BTW so if you haven't done that then uh here is a rooting tool. Now there is one step in the process I must warn you is very important that so many people overlook, when running fire flash you should see red warning text about the bootloader not being old enough to work and that it needs to be downgraded, there is a checkbox for doing this either above or next to the red text, if you don't check this and you hit flash you will reboot with a red screen you can't fix without a fastboot cable. Also like I said get the cm 11 ROM from here, and grab the corresponding gapps and stick them both on the sdcard ahead of time or you will be having fun using adb commands to push it to the device as it will bootloop.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
+Note: As of Amazon OS update 7.3.x+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2. If you want guaranteed success, use this tool to revert back to 7.2.3 before using the guide. You will need to flash a brand-new 7.2.3 on top to revert, so you will lose everything if you don't backup your files first.
++Note: As of December 2013, Hashcode updated the freedom-boot.img to Amazon 7.4.6 so there should be no more bootloops or any other issues like that for those running 7.4.6 or lower, but to be safe, revert back regardless. If your tablet is running anything higher than 7.4.6, you will run into issues when completing the guide. Again, if you revert back to 7.2.3 like I pointed to above, then you will have no issues. If you didn't revert, always make sure your tablet is running the same or lower version than Hashcode's freedom-boot.img.
The thread you linked to says otherwise. :/
The latest update it higher than 7.4.6.... (7.4.8 )
Sent from my Amazon Kindle Fire HD using Tapatalk
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
I'm rooting several Kindle Fire's and I've bricked 3 (of 18) and I just noticed on the last one where the commonality lies.... I used a a Downgrade Supertool and if when I ran that it got stuck in "FastBoot" and then I manually went into ADB Sideload mode and pushed the files using the SuperTool it bricked the device. But, when I connect it I can hear the chirp that it connects, but nothing shows up and it won't turn on.
They are the newest Kindle Fire 7" tablets (the ones that are in different colors). Please help! These are for a first grade classroom and I don't know how to fix them!
Danielle926 said:
I'm rooting several Kindle Fire's and I've bricked 3 (of 18) and I just noticed on the last one where the commonality lies.... I used a a Downgrade Supertool and if when I ran that it got stuck in "FastBoot" and then I manually went into ADB Sideload mode and pushed the files using the SuperTool it bricked the device. But, when I connect it I can hear the chirp that it connects, but nothing shows up and it won't turn on.
They are the newest Kindle Fire 7" tablets (the ones that are in different colors). Please help! These are for a first grade classroom and I don't know how to fix them!
Click to expand...
Click to collapse
Sounds like the wrong image may have been pushed. Recheck file identifiers and md5 checksum. Regardless, if you can't access stock recovery little can be done to revive bricked devices at present. Consider an exchange with Amazon given most/all should still be within warranty.
It was the same image I used with all the others... I just had to get to the ADB Sideload menu manually... I'm not sure what the actual difference was. I'm worried if I return three they'll be suspicious. Plus, I don't have access to the account in which they were ordered.
Danielle926 said:
It was the same image I used with all the others... I just had to get to the ADB Sideload menu manually... I'm not sure what the actual difference was. I'm worried if I return three they'll be suspicious. Plus, I don't have access to the account in which they were ordered.
Click to expand...
Click to collapse
Doesn't change the fact recovery is not possible at present. Not certain what happened; I never use automated tools for sensitive operations.
If unable to return best shelve them and hope a generic recovery method becomes available downstream.
Davey126 said:
Doesn't change the fact recovery is not possible at present. Not certain what happened; I never use automated tools for sensitive operations.
If unable to return best shelve them and hope a generic recovery method becomes available downstream.
Click to expand...
Click to collapse
Hope it's ok to piggyback on this question, since you mentioned recovery is not possible ... to be clear, I went the 5.1.4 -> 5.1.2 -> CM12.1 route, does this mean that this device can't even do the temporary TWRP boot using fastboot? (I tried and got the "unknown command" error).
If that is the case, what is the recommended way to do a full backup? I want to mess with build.prop and would like to back it up first.
blowbigchunks said:
Hope it's ok to piggyback on this question, since you mentioned recovery is not possible ... to be clear, I went the 5.1.4 -> 5.1.2 -> CM12.1 route, does this mean that this device can't even do the temporary TWRP boot using fastboot? (I tried and got the "unknown command" error).
If that is the case, what is the recommended way to do a full backup? I want to mess with build.prop and would like to back it up first.
Click to expand...
Click to collapse
Question doesn't belong in this thread but will offer a quick response; follow-ups should be posted in the Q&A section.
- you can not boot/install/use twrp or any other custom recovery
- if you can still boot CM use a well regarded backup app like Titanium
- FlashFire offers a more comprehensive backup but is unproven
- adb backup is another comprehensive solution but requires a tether
- build.prop tweaks to emulate another device are generally ineffective
- if you still want to tinker use a proper editor such as the one integrated into Kernel Adiutor (spelled correctly)