Related
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
I'm not sure really how to help, but if you can describe the last thing you were doing prior that will help people diagnose it. Were you rooted? Or trying to root? Did you try to modify any system files?
I have the same problem. I was rooted. I was trying to copy the vendor apk into system/ app folder. I think I accidently made copy of app folder, it said app copy then froze. I clicked system restore. did nothing.
Are you able to reach the system with adb shell at all? or not? If not, I think you are stuck sending it back to Amazon for repair/replacement. If you can, you should be able to use the same method you used to root to get /system RW again, and try to fix it up.
I don't know how to use ADB. I used the one click root method. My computer isn't recognizing the device when plugged in. Is there a step by step guide on how to fix it or will it be possible in the future?
If its not recognized, then its unlikely that adb will work. If I had a bricked device though...I would start reading and trying to get that working. If you really don't feel confident in messing around and trying to fix it, call Amazon and ask them to send you a new one.
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
what do you do so that KFTT state in bootloop?
can you take screenshot? or take a picture?
I am having the same problem.
any luck fixing it?
Hi, I am in the same situation. Here in Spain we have the KFHD since 4 days ago.
I rooted it correctly via ADB. I installed google play and installed several app's apparently without difficulties. The issue came after putting the Go luncher HD apk on system\app. After that I rebooted the device and appeared the two luncher options. So everything ok. I was moving around my new luncher and everything was ok, but suddenly the device rebooted and I had the same issue here explained. Bootloop and no factory default possible. Of course just rebooting didn't solve it. I have to say that the last thing I was doing before the sudden reboot was modifying permissions from SU. Maybe it's related, so don't touch anything from there. ADB was not working any more so very few things to try...
Amazon accepted a replacement (I just said what happened but not why) and now I'm waiting a new one.
Hope this can help.
Regards,
If you're willing to do a little work, you can try this recovery method: http://forum.xda-developers.com/showthread.php?t=1951254. Personally, I would just send in the device to be replaced, and not tell them the exact circumstances of how the problem happened. Amazon's generally pretty good about returns and replacements while you're still within warranty.
I shouldn't have restored factory defaults
I am in the same issue
The main mistake I made was selecting "Reset to Factory Defaults"
This automatically turns off the debug mode and with it stopped any communication between my PC and the Kindle Fire HD 7". Even the Factory cable I bought for £3.19 didn't help. The driver shows like it is installed correctly and my Kindle shows Fastboot on the screen when connected, but there is no communication.
I only got it for Christmas and I've goosed it. I am now hoping Amazon will be sympathetic and believe that it just started looping itself without me modding it.
When you reach the fastboot screen unplug factory cable and insert the usb that came with it. Then check your drivers to make sure they are Installed properly. Then use system Img restore tool to restore, follow directions exactly
Sent from my KFTT using XDA Premium HD app
Hello All! I was messing around with App Quarantine and ended up bricking my KFHD (not sure what I did because I was still messing around with it.) My KFHD is rooted but I didn't install TWRP or any type of recovery program. Is there any way for me to unbrick this or am I stuck with a fancy paper weight?
Ichigo said:
You guys should check the 1st gen. Kindle Fire Forums for similar problems and solutions.
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
[email protected]@dog said:
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
Click to expand...
Click to collapse
Technically, the factory cable will still work, even if there are ways to know that you shouldn't do some things (like number 4 in the thread in my signature).
Ichigo said:
Way to bump an old thread.
Click to expand...
Click to collapse
It was sort of a failed attempt, so what the heck.
[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
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
Hi there,
Firstly I apologise, this post may be a little vague, as am having trouble getting the truth out of my son. I was wondering if anyone might be able to help me identify what the heck he has done to his Kindle Fire HD 7"
When you turn the device on, despite initially saying Kindle fire HD, this text is soon replaced with a boot screen animation that simply reads "DROID".
When you begin to use the Kindle there is a small carousel of apps over the larger carousel. Also when you rotate the screen to landscape it doesn't seem to reorientate the display and only shows the top half of the screen. It also seems to crash and won't come out of the lock screen.
I am guessing he has tried to either root it or flash a custom rom, he says he installed an app called root master? But cannot see how an app would grant root access?
We bought this for him as a Christmas present, and whilst am sorely tempted to tell him "tough" as he's obviously tried to do something without fully understanding what he's doing, I would like to be able to sort this as soon as I stop being cross.
So whilst I appreciate this is all a bit vague, does anyone recognise any symptoms, and have any insight into what he might have done and/or installed and is there any sure fire method to get this back for him?
A couple of questions:
-> Is it the 2012 version with the camera and HDMI output, or is it the 2013 version that has neither of these?
-> Can you access the settings and enable ADB?
-> Can you solder or are willing to shell out $10-$15 to fix this?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
hi there,
Thanks for the reply.
We got it for him for Christmas 2012.
Can get to settings. I have enabled ADB (just to see if I could, and I can).
Does this mean I might not need a soldering iron?
Do not claim to be any sort of expert, so please assume no knowledge here.
But will carefully follow instructions if there are any.
Am hoping to be able to hand him back a working device when he's learnt his lesson.
Thanks again
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock. And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
SafinWasi said:
I would suggest you to use the Kindle Fire First Aid if fastboot works. That way you can go totally stock.
Click to expand...
Click to collapse
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
SafinWasi said:
And a few more questions:
Do you have the Android SDK installed on your PC? If yes,try using "adb devices" to see if it recognizes the Kindle
Click to expand...
Click to collapse
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
SafinWasi said:
[*]Shut down the Kindle. Boot it up. Do you see an orange Kindle animation only or a blue animation?
Click to expand...
Click to collapse
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
SafinWasi said:
I suggest you buy a factory adapter from Team BlackHat here if fastboot doesn't work.
Click to expand...
Click to collapse
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
SafinWasi said:
PS: Don't be too cross on him. It's perfectly understandable if he wanted to flash a custom ROM. I ended up hating Amazon after realizing what they did to Android....
Click to expand...
Click to collapse
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
silentbazz said:
Is this what is being described here?
http://forum.xda-developers.com/showthread.php?t=2096888
If so, I will have a look this evening..
I like the fact that it has "noob" in the post description.
Although I flashed a custom rom onto my Samsung Galaxy S2 a couple of years back (using ODIN) a lot of the instructions in this Kindle Fire section seem to be very confusing. I wish I'd known he was planning to do something like this, as I'd have read up on it for him (and, most likely warned him off, amazon look like they have locked down this tablet to a horrific degree)
Okay, that sounds a good first place to start. I don't think I have the SDK currently installed but I guess I can grab it again from google.
I take it if the SDK can "see" it we're halfway there?
Just to clarify:
The device is "quite" responsive.
It will boot up (although I cannot find anything on the internet about this boot animation that just draws the word "DROID" - if I could, I might be able to figure what he's tried to do at least) and you can sort of use it (although there are onscreen glitches as described above) and it freezes up when the screen locks (so you have to reboot every time it locks the screen). But, at least it's not totally D.O.A, I guess.
It does initially flash up Kindle..
I thought I had solved the problem with a factory reset last night (I'll admit for a second I cheered), but after initially showing Kindle Fire, it then starts going to this blue DROID animation..
Okay, cool I take it this is step three if the Kindle Fire First Aid doesn't work?
I am a lot calmer today, am sorry that the first post was written in "Angry Dad" mode
I was just annoyed that he tried to deny doing anything to his device, and claimed it was "just an amazon update" (when it was obvious it wasn't).
This is why I am hoping to fix it for him, it was a Christmas present after all, and I would like to (eventually, not right away) hand him back a working Kindle device.
I just wish I wasn't flying so blind.
Thing is I'm not 100% sure he know's what he's done, I think he's just blindly followed a YouTube video or similar and he's ended up with this.
I really, really appreciate you guys taking the time to reply to my post.
Thanks so much for reading and responding.
Click to expand...
Click to collapse
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
Although I have no idea how he got the Droid animation....
SafinWasi said:
Although I have no idea how he got the Droid animation....
Click to expand...
Click to collapse
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
silentbazz said:
Okay, apparently, he went to this 1mobile market to get a one click root app.
I have not been able to find the app myself, but am very worried that he's been downloading apps from an unofficial app store.
The change to the boot animation seems to have been achieved using a Xposed app (that requires XBlast?). It was after installing this, and changing the boot animation that he says the Kindle started to behave weirdly.
Have not had the time yet to sit down and go through the instructions provided, thank you for those, I will set time aside at the weekend as I don't want to rush it.
At least now I know where the weird boot animation came from
I provide this info as a warning to others.
Click to expand...
Click to collapse
1mobile is an OK place to download apps from. You just have to make sure the dev is reputable. XBlast can mess a tablet up if you play to much with it.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
SafinWasi said:
I agree. It's tricky,XBlast. Any progress?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
silentbazz said:
Alas, not good..
Am stumbling at the first hurdle really, have installed the AndroidSDK all okay but am trying to add the Kindle Fire drivers into the SDK as per amazon's instructions here .
But the SDK they describe doesn't seem to match the SDK environment I have installed (I have version 23.0.0.1245622 of eclipse installed, which seems to have a different menu structure to the one amazon describe?) and whenever I try and get
Eclipse to access the URL amazon has told me to (http://kindle-sdk.s3.amazonaws.com/addon.xml) I get the message "No repository found at http://kindle-sdk.s3.amazonaws.com/addon.xml"
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Hi! One click root app was probably called VROOT. VROOT is still not identified as safe as there may be malware, sorry :\ However if you have a FASTBOOT cable go on this website and you should be able to restore it without SDK.
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
by the way once choosing an "option" please wait for at least 20 minutes as restoring the device takes a long process.
silentbazz said:
Am really not sure what I'm doing wrong..
Click to expand...
Click to collapse
Your tablet still has fastboot access which means it's almost surely restorable. The flasher offered above will work and so will the System Restore Tool. You just run the bat and wait to be restored. Make sure your drivers are installed properly. Windows 8/7 64bit need to be put in test mode so your drivers will install right.
Windows is not going to let you do this until you disable device driver signature enforcement.
Disable device driver signature enforcement in Windows 7 read on. Windows 8 has different steps.
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.*
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."*
Note: This must be done on every bootup you want to install something not MS signed.*
B. For a more permanent solution.*
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now type these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.*
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. To exit test mode follow steps 1,2 and 3 in part B of my writeup and type these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS*
bcdedit.exe -set TESTSIGNING OFF
Now restart computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
SafinWasi said:
Okay,I'll guide you through a step-by-step tutorial to restore your Kindle.
Download and install the Android SDK. That is the first thing any Android modding guy must have. It provides you with the ADB and Fastboot executables which you're gonna need.
Download and install the Kindle Fire HD ADB drivers. You're gonna need them since the official Google drivers that came with the SDK are not supported by Amazon.
Modify your path variable. To do this,right-click on 'My Computer' and select properties. Click on "Advanced System Settings" and then "Environment Variables". At this point,you should copy the path to the tools and platform-tools folders of your SDK and paste them in the "path" system variable . If you want a video tutorial:http://www.youtube.com/watch?v=oaNM-lt_aHw
See if ADB and fastboot works. Open CMD from Run and type in ADB or fastboot. If it returns a lot of text,it's working.
Now type in:
Code:
fastboot -i 0x1949 getvar product
It'll return <waiting for device>
Turn off the Kindle and plug it in. If it boots into fastboot,you're good to go with KFFA
If it doesn't boot into fastboot,you'll have to buy a fastboot adapter or make one.
.
Click to expand...
Click to collapse
Okay, I got the amazon drivers installed on my machine, and had fastboot and adb working from the command prompt after adding all of the paths to the PATH environment setting.
I typed in:
Code:
fastboot -i 0x1949 getvar product
and I got the prompt <waiting for device>
However when I attach the device, it just boots (with the weird droid animation) - I cannot see anything to say that it has fastbooted. Does it display any different?
I have also typed adb devices and I don't think my PC is seeing the Kindle Fire HD as I get no devices shown in the List of Devices?
Does this mean I need a fastboot cable?
Would installing cyanogenmod on this be an option now? Or would that just make matters worse at this stage?
++ EDIT ++
Actually, uninstalled and reinstalled amazon adb drivers, and retyped:
Code:
adb devices
and it output:
D025A0A0241220KP device
so tried the fastboot -i 0x1949 getvar product command again, but still the device booted normally
SafinWasi said:
Don't do that. Just download my Flasher and extract it. There is another zip inside,which has the drivers. Just install them normally.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
By the way just wanted to say thanks for providing the Flasher.
Amazon drivers extracted and installed like a charm (once I allowed them to install to the default location)
silentbazz said:
Does this mean I need a fastboot cable?
Click to expand...
Click to collapse
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The only time you don't need one is if you can access the OS and you have functioning root. If you don't have this then you must have a fastboot cable. If you have a Motorola cord laying around try that.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
silentbazz said:
Ahh okay, I understood that I might be able to get the device to enter fastboot without a cable.
I must have read this wrong.
Okay, as I am not in the United States I am guessing eBay.co.uk is my best option?
Will something like this do the trick?
Click to expand...
Click to collapse
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Should work fine.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
silentbazz said:
Okay, great, have got one ordered, so will hopefully be able to get this sorted soon.
A sincere thanks to everyone who has offered sage advice above.
Some ace tips here, hopefully I'll get this sorted for him
Thanks again!!!!
Click to expand...
Click to collapse
You're welcome. Keep us updated.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
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)